I finally bit the bullet and installed Visual Studio 2008 Pro Beta 2 on my development PC. Couldn't resist anymore with all the buzz in the ASP.NET blogosphere and I thought it would be safe enough since
- You can install it alongside VS 2005 (in theory - it is a beta)
- With VS2008 "Multi-Targeting" you can use VS2008 to work on ("target") a ASP.NET 2.0 web application, even using ASP.NET AJAX 1.0 extensions. Supposedly, you can still get most of the cool features of VS2008 to work while targeting .NET 2.0.
<asp:ScriptManager ID="sman" runat="server">
<asp:ScriptReference Path="~/scripts/protos.js" />
I'll update this post if I figure anything else out along the way. I really should be getting a paycheck from Microsoft. :-) But then, that is the brilliance of the community driven development that Microsoft is tapping into so heavily now - and I can't be angry at them for that, since I have benefited from that a lot more than I have contributed.
I got CSS intellisense almost completely working. I was using a declaration in the System.Web.Pages section of my Web.Config to bring in the App_Theme\default information from my project, including default.css; this was not working for the CSS features. I had to create a manual <link rel="stylesheet" /> in the <head> of my master page, and then it started working slowly but surely. Another thing I'll have to remember on deployment. Good thing I have this all written down somewhere. :-)
The one thing that doesn't work is typing class=" doesn't bring up an intellisense box like it is supposed to when a StyleSheet and classes are present for a page. Ctrl+Space doesn't help either of course.
Post a Comment