I was struggling this morning with issue in simple NAnt script, I was trying to uses <exec> task to call msbuild tool.

Ok quick brief on the issue, NAnt 0.86 Beta 1 does not able to run its solution task to build Microsoft Visual Studio solutions against Visual Studio 2008 solution files, however it can build solution for .NET 3.5 Framework. so I found two solutions –till now-, both of them are using MSBuild tool to build my solution with two different ways; first one is to use NAntContrib as extension for NAnt and use its msbuild task to fire msbuild tool – I did not try that yet –, and the other one is to use NAnt exec task to call msbuild tool and throw to it my solution file as parameter; and while I am try that I found issue, I need to add /p:Platform=”Any CPU” as msbuild command switch but how to add double quote to task attributes, it fails if I wrote:

<exec program="${framework::get-framework-directory
      (framework::get-target-framework())}\msbuild.exe"
      commandline="mysolution.sln /p:Platform=”Any CPU”"/>

Fortunately, I found nice simple post to solve this issue by adding property to NAnt script with double quote as value and use it in my command as following:

<property name="dbl_quote" value='"'/>
<exec program="${framework::get-framework-directory
      (framework::get-target-framework())}\msbuild.exe"
      commandline="mysolution.sln
      /p:Platform=”${dbl_quote}Any CPU${dbl_quote}"/>

It is nice and quick solution.

There is a strong desire in our group to move towards distributed version control systems specifically mercurial. As I spend most of my time working on the Chemistry Add-in for Word 2007 (Chem4Word) I have been using Visual Studio 2008. This doesn’t come with source control support out of the box – but you can (and we have) added on team foundation server support but this isn’t distributed and quite frankly sucked.

I have spent the last couple of days investigating other options and having got a good solution up and running thought I should share this with the world. This definitely isn’t meant to be an introduction to mercurial in general and I won’t be explaining all the terms (good intros are available from the mercurial website and elsewhere). I will be giving both command line and GUI instructions.

Installing VisualHG

The instructions on the VisualHG site are pretty good – but you only need to go through the first three. Basically you need to download and install TortoiseHg and then VisualHG.

Next make VisualHG the current active Source Control Plugin in Visual Studio 2008. <Tools> -> <Options> -> <Source Control>. Set the value of the drop-down list (Current Source Control plug-in) to <VisualHG>.

How to create a new repository and add it to source control

Open Visual Studio 2008 and create a new solution (in my case I went for a Console Application called cs-walkthrough under C:\projects\c# and I didn’t want a new directory for the solution)

In a command window change directory so you are in cs-walkthrough.

>hg init

this will create the .hg directory

create a file called .hgignore as a sibling of the .hg directory the contents of the file should be:



syntax: glob

*.csproj.user
obj/
bin/
*.ncb
*.suo
_ReSharper.*
*.resharper.user

Create a project on bitbucket with the same name as the solution (doesn’t have to be but will make things easier). So in this case I now have a publicly viewable repository on bitbucket http://bitbucket.org/jat45/cs-walkthrough.

Now create a file called hgrc under the .hg directory. This file should contain the following text:

[paths]
default = http://bitbucket.org/jat45/cs-walkthrough

[ui]
username = Joe Townsend

where jat45 should be replaced with your bitbucket id and cs-walkthrough should be replaced by the name of the bitbucket repository you just created.

From here on in you can do everything either from the command line or from within Visual Studio. I will give both commands (to access the VisualHG commands right-click on any of the files in the solution). All the command line commands should be run from the [cs-walkthrough] directory.

>hg status

or <HG status> from VisualHG

We want all these files under source control so either use

>hg add
or select all the files from the GUI and click Add then close the window

To commit these additions either use
>hg commit -m "initial commit"
or commit using <HG Commit>

Now push these changes to bitbucket

>hg push
or <HG Synchronize>(this will allow you to push, pull and see the incoming and outgoing changes).

Warning

Before committing or pushing changes you must make sure you build the solution first. This ensures that the [project].csproj file is correctly updated.

Getting an existing project

This is much easier than creating a new repository from scratch. Once again though we are back to the command line.

Change directory to the parent of where you would like the new project repository to be checked out to. In my case this is c:\projects\c#.

I am now going to get a clone of the cs-walkthough code from bitbucket but put it in a new location.

c:\projects\c#>hg clone http://bitbucket.org/jat45/cs-walkthrough my-new-source-dir

You can use the same command because the project is public so you can access the source code but not commit.

So I think that is it. You can do all the usual, push, pull, diff and so on either from the command line or from the VisualHG add-in. The one only thing that must be done from the command line is the initial clone or init. I am also investigating if everything works in VS2010 – so far no problems but if I run into any I will update you.

NAnt is helpful, open source, and free tool for automated .NET-build process, same as Ant but it is targeting .NET frameworks rather than Java, and according to Wikipedia the name NAnt is coming from Not Ant

NAnt allows you to build a script (XML Script) configuring tasks and dependencies with reach NAnt functions, expressions, data types etc…

Alright, going back to this post purpose; here you are the steps to allow NAnt intellisense in VS 2008 (I believe for other VS versions too) in Windows operating systems.

• Download Nant binaries or source code from here, I will go with latest one NAnt 0.86 Beta 1.
• Extract the compressed folder and follow NAnt installation steps as explained here.
• Copy nant.xsd file from extracted folder (<Base installation directory>\schema\nant.xsd)
• Paste this file into XML schema folder in Visual Studio installation directory; it should be as following in x32 bit operating systems (C:\Program Files\Microsoft Visual Studio 9.0\Xml\Schemas) or (C:\Program Files (x86)\Microsoft Visual Studio 9.0\Xml\Schemas) in x64 bit operating systems.

You should be done now with those steps, do start new NAnt XML script and get use of Intellisense, create new XML file in VS 2008, and in the root node <project> add the attribute xmlns=” now you should see NAnt schema in the drop down list as bellow:

And now you have NAnt XML intellisense enabled in VS 2008 as bellow:

Disclaimer in the beginning itself : I am a java professional basically and Java J2EE and RDBMS is my bread and butter.

Still, in the due course of time and out of passion for different programming languages, to gain versatility, and because of mood swings I get rather frequently than rarely, I have a fair bit of flair for PHP, Ruby, Python et al…

C and C++ was my introduction to programming language world, some 10 years back, but never got chance to work extensively on those. Had C# basic knowledge as such, but nothing concrete again. That sums up .Net.

But recently got into the project which has its backend in Java and client written in C#. Want to take full use of technologies.

Intsalled .Net framework 1.0/2.0 and 3.5 which comes bundled with VS2008. First thing first, being a Eclipse/Idea guy all along, spent my hours making VS too similar to Eclipse for me. Second, I always start a project with “debug”. Now I am not aware of the theories regarding whether its right or wrong to do so, but yet this is my modus operandi, so I set sail on my debug journey.

Got my debug working. Found out two-three things in first hour, these are:

1. Just like jars, here the things resolve around dlls.

2. the interface to include those dependencies though are pretty bad.

3. VS is much much slow than Eclipse in my humble opinion. You can say I knew it by birth, but now I can definitely write so too.

4. Strange things happen in .Net world (Pardon me, I have heard that too many times that it has definitely affected my viewpoint). My project was supposed to work from the word “go”, but it didn’t. Got some System.DLLexception: and it was not able to load some DLL we are creating in the project through NAnt.  (It was my first experience with NAnt too, something, a very little tiny thing about that in some other post too.) so, DLL was there. But why the f***, it was not able to load then. Got to know it might be because of some other DLLs which this DLL is dependent on. Fine. I thought I will check that. got to know about dependecnychecker, run it and to my surprise and irritation found that whatever dlls it require are present in my system, their path is already included. What the hack! Then, just it happens, sometimes some idea strikes by lightning, I thought to give VS a restart and viola! (Questions for experts here first: I have seen these kind of things sometime happening with Eclipse too, not with jars, is it VS issue or some crap of .Net?)

5. Shortcuts with VS are so bad, I say.

6. Good learning,  and my learning starts with the DLLimport sort of keywords, already a stuff of intermediate level I guess(other experts can confirm or take me out of my fairy tales)

7. Did learn about setting arguments, setting output directories, Assembly Infos in the first go. first two much like Java, not a big deal!

Hope I will get more insight with already running (although crappy)  code at my disposal.

One last question: What’s the best framework to embed MVC in window Form applications?

And what the hack is Resharper?

If you can’t see default Silverlight control in Toolbox, run “devenv /setup” or “/reestsettings” in Run or “Visual Studio 2008 Command Prompt”

I was expecting that Visual studio will do the magic for me and enable Intellisense for JQuery javascript library automatically once I add the library and referenced it in my page – naive, right?- anyways it did not happen of course, so with a quick look to the internet and beloved Scott Guthrie blog I found that I need couple of steps to enable it; It is easy and quick steps so I liked to share it with other naive developers .

1. Install Visual Studio 2008 SP1.
   This service pack adds richer javascript intellisense support for Visual Studio 2008, you will find it here.
2. Install Visual Studio 2008 Patch KB958502 to support “-vsdoc.js” Intellisense files
   This patch apply for VS2008 SP1 and VWD Express SP1, enables Visual Studio to detect “-vsdoc.js” files when javascript library is referenced and use it to enable Javascript Intellisense. This patch can be found here.
3. Download the JQeury Visual Studio doc file.
   You can find this file with ASP.NET MVC package as it is included by default or you can find it in JQuery official web site as Visual Studio documentation.
4. Save “vsdoc.js” file in the same directory
   Save the Visual Studio documentation file in the same directory of the JQuery library, and then you can reference the library in your page as below:
   <script src="../../Scripts/jquery-1.3.2.js" type="text/javascript"></script>
   start now to use the Javascript Intellisense feature.

Important Trick:
Sometimes we use partial views or user controls in our project and we do not to refer to Javascript library within it, we usually refer to it in Master page or the parent page; Visual Studio has no way to know this script is available in for the user control or the partial view, thus Javascript Intellisense will NOT be enabled in these files, to enable Javascript Intellisense in the partial/user control there is a useful trick by reference the library surrounded with If(false) statement which will never be rendered in the run time, but still provide Javascript intellisense in the design time.
<% if (false)
   { %>
   <script src="../../Scripts/jquery-1.3.2.js" type="text/javascript"></script>
<% } %>

References:

• http://weblogs.asp.net/scottgu/archive/2008/11/21/jquery-intellisense-in-vs-2008.aspx

Sau khi chuyển sang dùng VS2008 SP1, tôi gặp một lỗi ngớ ngẩn và rất khó chịu, nó làm giảm hiệu suất làm việc rất nhiều.

– “Step into” (khi bạn nhấn F11) hay “Step over” (khi bạn nhấn F10) không dừng lại ở các breakpoints.
– Đôi khi nhấn F10 và F11 thì VS2008 cư xử như ấn F5. —-> bạn sẽ không debug được

Đó là một lỗi của M$, mời xem tại đây: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=365666 và https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=368650

Cài Hotfix sẽ chữa được lỗi này:

http://code.msdn.microsoft.com/KB957912/Release/ProjectReleases.aspx?ReleaseId=1796 (15.5MB)

Hy vọng giúp được các bạn.

Bổ sung:

Nếu bạn chạy windows 64bit (Vista 64, Windows 7 64 …) thì khi cài đặt có thể bị lỗi. Nguyên nhân thì chưa xác định rõ ràng (tôi đoán là do trên các bản win này, VS được cài ở Program Files (x86), chứa ký tự đặc biệt nên bản cài cho hotfix bị lỗi (xong trong log thì thấy) khi detect đường dẫn)

http://codepoet5150.com/2008/09/12/visual-studio-2008-sp1-setup-failure-on-64-bit-vista-solved/

Giải pháp: bạn disable ổ CD/DVD đi thì sẽ giải quyết được vấn đề

- bỏ các ổ ảo, virtual drive nếu có
- bỏ ổ CD thật (chuột phải vào My Computer, Manage, Disk Management, disconnect ổ CD hoặc remove driver letter/path đi)

El equipo Microsoft de Visual Web Developer ha creado un nuevo esquema de Intellisense el cual se puede agregar a VS 2008 o VWD Express 2008 para así disponer de Intellisense y validación para los elementos HTML 5.

Nota: El esquema es solo para el “marcado” (tags) HTML, aún no para el DOM2 para el Intellisense de Javascript.

Para instalarlo, dirigirse a: HTML 5 intellisense and validation schema for Visual Studio 2008 and Visual Web Developer, descargar el adjunto: html5.zip y seguir las instrucciones, las cuales se reducen a copiar el archivo html_5.xsd a “%ProgramFiles%\Microsoft Visual Studio 9.0\Common7\Packages\schemas\html” y combinar el archivo *.REG correspondiente al tipo de S.O. y edición de VS 2008.

Una vez realizado lo anterior, podremos seleccionar “HTML 5” en el cuadro desplegable de esquemas de validación, y los elementos HTML 5 aparecerán en el Intellisense y la ventana de propiedades.

Si se preguntan ¿en que browser podemos probar HTML 5? La respuesta la podemos leer en: Browser support for CSS3 and HTML5.

Actualización (23-Nov): El equipo de VWD ya ha corregido la información y los archivos *.reg erróneos para VWD Express 2008, por lo que, si descargan el archivo html5.zip actualizado, ya no es necesario hacer lo que sigue a continuación.

[ATENCIÓN]

El post original indica que si contamos con un S.O. de 32 bit y VWD Express 2008, habría que cambiar en el path “Microsoft Visual Studio 9.0” por “Microsoft Visual Web Developer”, lo cual al menos en mi caso no fue necesario. Es decir, aún con VWD Express 2008 utilice el path indicado para VS 2008.

Por otra parte, también existe un error en el archivo *.REG correspondiente (HTML-5-Schema-Reg-x86-VWD.reg), mismo que se tiene que editar para que funcione correctamente.

La corrección consiste en cambiar “VisualWebDeveloper” por “VWDExpress” en la clave de registro:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualWebDeveloper\9.0\Packages\{1B437D20-F8FE-11D2-A6AE-00104BCC7269}\Schemas\Schema 23]

De modo que el archivo HTML-5-Schema-Reg-x86-VWD.reg finalmente queda de la siguiente forma:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VWDExpress\9.0\Packages\{1B437D20-F8FE-11D2-A6AE-00104BCC7269}\Schemas\Schema 23]
"File"="html\\html_5.xsd"
"Friendly Name"="HTML 5"
"URI"="http://schemas.microsoft.com/intellisense/html-5"

Guardamos el archivo y lo combinamos en el Registro de Windows.

Nota: Supongo que ésta misma corrección debe hacerse en el archivo para 64-bit, pero no lo puedo asegurar.

So as part of my experiments with creating and installing Work Item Custom Controls for use in Team Explorer 2010 I inevitably wanted to be able to attach a debugger to an instance of Team Explorer 2010 to interrogate the Work Item object model at runtime.

I’ve done this before for Team Explorer 2008 and wasn’t anticipating any problems. The basic setup can be obtained using these instructions on the Team System Notes blog.

Having followed these instructions I hit a bit of a roadblock. It turns out that VS2008 doesn’t like attaching a debugger to a VS2010 instance. If VS2010 is setup as the start-up application then an error is thrown when starting the project: “The debugger’s protocol is incompatible with the debuggee“. I’m guessing here, but I’d assume that the issue is that VS2010 has been compiled using .NET 4.0, and as VS2008 only supports up to .NET 3.5 the debugger is unable to correctly attach to a 4.0 managed process. I had hoped to keep this machine (the primary one I use for work) free of the full VS2010 components … however having hit this issue I’ve had to download and install the beta 2.

Anyway, the upshot is that installing VS2010 and attaching the debugger to another VS instance from there solved the problem.

If you’re getting the infamous error:

A problem has been encountered while loading the setup components. Canceling setup.

Use this tool to wipe the lot

http://msdn.microsoft.com/en-us/vstudio/bb968856.aspx

This Auto-Uninstall Tool uninstalls ALL components installed with Visual Studio 2008 products, including Visual Studio Express Editions, Visual Studio Team System, Visual Studio Professional. This tool won’t uninstall shared components between Visual Studio 2008 and Visual Studio 2005.

So before I dive into my world changing ASP.NET MVC app, I figured I’d take some time to explain very simply how to set up some SVN integration in VS2008. Ready? Don’t blink ’cause you might miss it:

1. Beanstalk – http://beanstalkapp.com/

Follow the cues to set up your free subversion repository, you won’t need help navigating their site, it’s super simple.

2. TortoiseSVN – http://tortoisesvn.net/downloads

This isn’t really necessary, but I like it just in case I’m in a windows explorer window and happen to want to commit something. Download the version for your appropriate cpu (32/64). Double click and hit next until it asks you to reboot. At that point you should reboot. Now you’re almost there, I mean you can hit up your beanstalk repo straight from the windows file system by right clicking the whitespace on a windows explorer window and clicking “SVN Checkout…”: but we want to never have to leave the IDE so on to step 3 we go.

Tortoise SVN Checkout...

3. AnkhSVN – http://ankhsvn.open.collab.net/

On the right you’ll notice the download link for version >= 2.1. Once it’s downloaded, close visual studio, double click the installer, next, next, next. Once it’s done installing open up visual studio and you’ll notice a new tab at the bottom of the window “Pending Changes”. If you don’t, that’s fine just click on “View” then click on “Pending Changes”:

AnkhSVN Pending Changes Pane

4. Time for the secret sauce.

Now, let’s put these awesome tools into action. Right click on your solution in the solution explorer and click “Add solution to subversion”:

Adding your solution to subversion

A pop up window will come up, just enter in your repository URL:

AnkhSVN asking you for your repo URL

(which can be found on your dashboard at beanstalk on the right under “Repository URL”) and once you connect, just hit OK and you’re good to go.

After this intial upload, your solution explorer will reflect which state your files are in:

• Blue check mark: you’re synced up with the repository
• Red rectangle: you’ve made changes that haven’t been committed yet

Ankh-ified Solution Explorer

Once you edit a file and you want to upload changes to the repo or download someone else’s changes, just go down the “Pending Changes” tab on the bottom of VS and hit “Commit/Update” respectively.

Nesting the aspx files and cs files in Visual Studio 2008 and above.

When we move the ASPX and code behind file to any new folder in Visual studio. Then the file nesting in the folder in Visual Studio is incorrect. ASPX represents one file and cs file represents another file. Consider if you have large number of pages then each will represent twice. In order to avoid this we have option in Visual studio Solution Explorer for “Nesting Related Files”

After clicking this Visual Studio Project update the solution explorer and show the nested files exactly.

Avoid multiple of instances of Visual studio Development server

While working with Visual Studio Development server. In all previous versions of Visual Studio we have auto assign port values.

But in Visual Studio 2008 and above. We can set the port values other than the default values.

Sometimes on some developer boxes either Windows firewall or custom firewall blocks a bunch of ports… In this situation Web Development Server tries to hook to one of the blocked ports port and is not allowed. In the process the Development Server lands up crashing. Next time it tries to assign itself to another dynamic port and the same thing happens. As a result there are various tray icons created even though the Web Development Server exe has actually crashed. So that is the reason multiple reason of web servers running without any use.

This can be solved by running the Development Server in specific ports.

After re-arranging Visual Studio windows and moving my Output window to my 2nd monitor, my web project started crashing after it was built, giving an error BEX in msenv.dll, and an error for msenv.exe was logged in the Application Event Log. After some searching I came across a post referencing a hotfix for similar issues under KB960075, posted here. After downloading and installing, the issue was resolved. A new msenv.dll is placed onto the system that fixes the issue.

Nested Master page support

Master page support is the pretty useful feature in ASP.NET2.0.Now we can create the nested master page information.

Consider the scenario where the page has one base master page for the whole website and the another master page which uses for most of the pages in your web application. So here we can inherit the base master page in the another master page used by any aspx page.

One of the scenarios that ASP.NET 2.0 supports is the ability to have “nested master pages”. where we can create a root master page for a site that defines a site’s overall layout, and then create nested master pages that are based on the root master and further customize the layout

There is tremendous flexblity to Web UI projects.

I have attached the sample nested master page application in this post. Right click and save file as rename the file pdf to rar and open in VS2010 IDE

MultipleMasterPage

I saw in many application C# file. Lot of namespaces are referred. To avoid this in VS2008 and above IDE we have a feature called Organizing.

Right click in IDE and go to "Organize usings" in this we have

* Remove unused strings

* Sort usings

* Remove and sort

We can remove the unused namespaces and can sort the namespaces according to the order.

Here in this example I am using only System.Collections.Generic

Passo a passo de como instalar o Firebird DDEX no Visual Studio 2008:

1 – Baixe e instale o Firebird ;

2 – Baixe e instale o cliente do Firebird. NET, versão 2.5.0 for .NET 3.5/2.0;

3 – Abra  o Visual Studio 2008 Command Prompt e digite o seguinte :

gacutil /l FirebirdSql.Data.FirebirdClient

o retorno será parecido com :

Microsoft (R) .NET Global Assembly Cache Utility.  Version 3.5.30729.1
Copyright (c) Microsoft Corporation.  All rights reserved.

The Global Assembly Cache contains the following assemblies:
FirebirdSql.Data.FirebirdClient, Version=2.5.0.0, Culture=neutral, PublicKeyTo
ken=3750abcc3150b00c, processorArchitecture=MSIL

Number of items = 1

anote o número de versão, Culture e PublicKeyToken.

você tambem poderá obter esta informações abrindo o windows explorer e ir no diretório C:\Windows\assembly e no assembly FirebirdSql.Data.FirebirdClient ver as suas propriedades (clicar com o botão direito do mouse e ir em propriedades).

4 – Baixe o provedor DDEX Firebird e descompacte todo o arquivo para o diretório C:\Program Files\FirebirdClient. (você poderá descompactar em qualquer outro diretório.)

5 -  Modifique o arquivo Machine.config (C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG, configuração válida para .NET3.5 também). As mudanças:

* Após a tag <configSections> inserir esta linha:
<section name=”firebirdsql.data.firebirdclient” type=”System.Data.Common.DbProviderConfigurationHandler, System.Data, Version=%Version%, Culture=%Culture%, PublicKeyToken=%PublicKeyToken%” />
* e após a tag <DbProviderFactories> inserir esta linha:
<add name=”FirebirdClient Data Provider” invariant=”FirebirdSql.Data.FirebirdClient” description=”.Net Framework Data Provider for Firebird” type=”FirebirdSql.Data.FirebirdClient.FirebirdClientFactory, FirebirdSql.Data.FirebirdClient, Version=%Version%, Culture=%Culture%, PublicKeyToken=%PublicKeyToken%” />

ATENÇÃO: substituir pelas anotações do passo 3:

- %Version%
- %Culture%
- %PublicKeyToken% .

6 – Edite o arquivo FirebirdDDEXProvider32.reg  ou FirebirdDDEXProvider64.reg de acordo com seu sistema. ( localizado onde você descompactou o provedor DDEX Firebird de acordo com o passo 4). Substituir no arquivo .reg % Path% com o caminho para os arquivos DDEX (onde você descompactou o provedor DDEX Firebird – não esqueça as barras invertidas em dobro! ) Importar este arquivo .Reg para o registo (basta clicar duas vezes sobre ele.)

7 – No Visual Studio 2008 Command Prompt registre o assembly FirebirdSql.Web.Providers.dll :

gacutil /i <assembly_path>FirebirdSql.Web.Providers.dll

e substitua <assembly_path> pelo caminho do assembly no meu caso ficou

gacutil /i C:\Program Files\FirebirdClient\FirebirdSql.Web.Providers.dll

Opa, vamos lá

1) Instalem o Visual Studio, nós vamos usar o 2008 como padrão.

Você pode pegar a versão Express ( C++) na net ou pegar a versão Professional em sua faculdade. ( utilizando a licença Student )

Link : Microsoft Visual Studio C++ Express

2) Baixem o msys-1.0.11-RC2, e extraiam no C:  .

O msys é o minimal system ou seja ele é o sistema básico para compilação usando comandos do BASH do UNIX e ele se integra ao DOS.

Link : MSYS
Uma vez instalado adicionem nas VARIAVEIS DE AMBIENTE no item PATH

C:\msys\bin;

3) Baixem o pspsdk-setup-0.9.5 ( essa é a versão mais nova, com o a versão do SDK mais sincronizado com o SVN do Ps2dev.org, que é quem faz o SDK open)

Link: PSPSDK

Instalação classica ao estilo windows, porém na tela de selecionar os componentes marcaquem todas as opções

->PSP DevKit

->SDK Samples

->PSP Link

->HTML Documentation

->Basic Devpacks

->Eclipse CDT 5+ Support

->Visual Studio Support

->Man/Info Pages

O local de instalação é o padrão C:\pspsdk

4) Vamos Instalar a OldSchool Library for PSP, ate agora, foi a melhor lib que achei para PSP com mais recursos e mais otimizada.

Link: OSLib

Extraia o ZIP em C:\pspsdk

Vá ate a pasta INSTALL e execute o BAT Install_pspsdk.bat, no Windows XP funciona certinho, porem no Vista eu reparei que acontece alguns erros na hora da copia, mais nada serio, só você abrir o BAT e ver para aonde os arquivos seriam copiados e fazer isso na mão.

Agora vamos adiconar o suporte da biblioteca ao Visual Studio.

Vá ate a pasta PC existe um BAT Install.bat, abra ele no bloco de notas e cheque se a variavel está setando o caminho certo da sua instalação do Visual Studio, atualmente está setado para C:\Program Files\Microsoft Visual Studio 9.0\VC, se estiver certo feche e execute o BAT, se tiver errado altere e execute o bat.

Pronto instamos a lib.

4.1) Copie a pasta TOOLS da OSlib para C:\pspsdk, são ferramentas da biblioteca para tratar Fontes e arquivos wav.

Parabéns o sistema esta pronto para compilar

Proximo tutorial -> Criando seu primeiro projeto.

Javascript Debugging:-

In the VisualStudio 2008 and above(Visual Studio 2010) we have the feature called Javascript debugging feature.Normally everyone will face the issue in javascript that is there is no debugger for javascript. But now we can debug as like our server side coding.

Also Visual Studio 2008 and above support intellisense for javascript coding.

Here We can write any inline scripting or external javacript files. Intellisense and debugging will support for all the files.

We can even link to any external files like AJAX client behaviour, AJAX client control, AJAX client library.

The debugging will happen in server side code in the temporary file which is in the smart document navigation within the solution explorer.

The javascript that is sent down to the browser client is dynamically generated on the server(for example: with scripts that are stored as resources within compiled server controls – like ASP.NET AJAX UpdatePanels and control extenders).

We can see our script values in local and watch windows after the breakpoints.

Debugging:-

Windows Internet Explorer:-

I have installed Windows 7 x64 RTM in my work machine and… Surprise! Team Explorer wouldn’t work.

The settings were disabled and when I tried to connect to a server BOOOOOM!

This is the kind of errors that I love.

After uninstalling and installing and reinstalling and again installing VS2008 and Team Client and… nothing worked.

Finally, after searching everywhere, I found in the msdn forums someone that had a similar problem. What a relieve, I wasn’t the only one (it seems a smaller problem when you aren’t the only one with it).

As a solution, K. Renno indicated to run a command to skip loading some packages:

devenv.exe /resetskippkgs

Or to generate a report:
devenv.exe /resetskippkgs  /log C:\devenv-log.txt

After that, Visual Studio could start normally without using the /resetskippkgs setting.

Good Luck!

R.

From Microsoft Connect:
(https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=478117)

Until Microsoft come up with an official solution there is a working workaround for this problem.

This problem only appears to affect people who have not got Visual C++ Installed.

1.) Download VS90SP1-KB971092-x86.exe from here …
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=294de390-3c94-49fb-a014-9a38580e64cb
2.) Start the installation VS90SP1-KB971092-x86.exe
3.) Wait for the error message to come up – DO NOT CLOSE THE WINDOW!
4.) Copy the temp. folder where the patch has been unpacked to a new folder, for example onto your desktop.
5.) Close VS90SP1-KB971092-x86.exe that you started in 2.)
6.) Navigate to <drive>:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools and find vsvars32.bat.
7.) Change the permissions on the file to allow everyone to edit it.
8.) Start VS90SP1-KB971092-x86.msp from within the saved folder and the process should complete.