Jim Zimmerman - ASP.NET, MVC, Ajax and ORM

I was preparing for my session for Jacksonville Code tonight which is coming in a few days and noticed that my JavaScript intellisense no longer worked in Visual Studio 2008 beta 2.  Since part of my session requires that intellisense works and the fact that it is so much easier to write JavaScript, I was in a little bit of a panic.  I looked up the problem in Google and found this post, 

http://blogs.msdn.com/angus_logan/archive/2007/07/30/visual-studio-2008-beta-2-not-showing-your-javascript-intellisense-intellicode-syntax-highlighting.aspx

Basically two registry entries that must have gotten messed up when I uninstalled beta 1 and installed beta 2:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\CLSID\{014E9A41-54E5-44ED-B15E-EFFA8758BFFC}]

"CodeBase"=file:///C:\\Program Files\\Microsoft Visual Studio 9.0\\Common7\\IDE\\Microsoft.JScript.AuthoringServices.dll

and

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\CLSID\{014E9A41-54E5-44ED-B15E-EFFA8758BFFC}\InprocServer32\9.0.0.0]

"CodeBase"=file:///C:\\Program Files\\Microsoft Visual Studio 9.0\\Common7\\IDE\\Microsoft.JScript.AuthoringServices.dll

Gotta love the community! 

Thanks!

After I installed Visual Studio 2008 beta 2 (Orcas) and the new TFS explorer, I was trying to export my tasks to an excel file from Visual studio 2005 and encountered this error:

It says there is a problem with the installation of the Visual Studio 2005 Team Foundation Office integration components.   Luckily I was able to export the tasks to excel using Visual Studio 2008 beta 2, but now when I want to integrate with office and TFS I need to use the new beta.  I hope this is the only issue I run into, but I will keep you all informed as I run into issues.  Overall, I like the new beta, but am having a hard time figuring out when to make a new project use it as I will need to have all of my developers use it also for a particular project since we can't open the projects in both instances.

I just came across this list of issues with Visual Studio and Vista.  For those of you that dared to jump on Vista on your development machine you will like this list. 

One thing to note is that to debug properly in Visual Studio you will have to run the application as administrator.  I pointed this out in an earlier post, but also pointed out how to run as administrator all the time form the user access control property.  Well this is fine, but it is nice to have the access control turned on.  I turned it off so that id did not have to remember to right click and select "run as administrator" every time I launched a new instance of VS2005.  Anyway, here is a way to make Visual Studio and just about any other program run as administrator automatically.  Right click your shortcut and you will see this window.

Click the advanced button and then make sure the checkbox for Run as administrator is checked. Now whenever you launch VS 2005 then debugging will work without having to remember to right click the shortcut every time you launch it.

yeah, SP1 is finally here and has over 1000 bug fixes.  I hope they have fixed some vista issues also in the beta I saw up there after you apply service pack 1.  I could not get to it yet, but will have to update to sp1 first anyway. 

You can get all the service pack here.  Happy downloading!  I hope it doesn't break anything. It has to fix more things than it can break, I would think at this point.