Where can I download the MVC 3 Beta Futures?
View Complete Post
Version 2. 0 of the MicrosoftÃÂ® . NET Framework makes numerous improvements at various levels in the Web services protocol stack. In addition, better tool support and an increased focus on interoperability make your life easier.
MSDN Magazine April 2005
When the Web site used to collect customer feedback about the Visual Studio .NET beta needed an update, the Visual Studio team saw a good opportunity to implement, deploy, and showcase a real-world site using .NET technologies. This article covers the migration of the Web site, beta.visualstudio.net, from components written in Visual Basic 6.0 and ASP hosted on Microsoft Internet Information Services (IIS) 5.0 to ASP.NET and the .NET Framework. The choices of technologies to be incorporated, along with issues such as validation, security, and authentication, are all discussed. Both existing components and the new components written in JScript and ASP.NET that were used to migrate the site are also explained.
MSDN Magazine September 2001
MSDN Magazine February 2001
We are attempting to test out a website written in VS2003/.Net 1.1 in VS2005 Beta 2/.Net 2.0. Our main problem at this point is that certain classes are not being recognized when they are referenced in other files not in the same directory as the class file.Example:A Framework.cs file under \Applications is inherited by several other webpages. It resides under the namespace Company.WebSite.Applications.Another class, SearchHistories, is in \Applications\CrackHistory directory. The namespace of SearchHistories class is Company.WebSite.Applications.CrackHistory. SearchHistories inherits Framework. Under .NET1.1, there was no problem with this. However, in VS2003, a compile error states "The type or namespace name 'Framework' could not be found (are you missing a using directive or an assembly reference?) C:\WEB\Applications\CrackHistory\SearchHistories.aspx.cs".The immediate solution is to copy the Framework.cs file from the Applications directory and copy it into the Applications\CrackHistory directory. Then the error goes away. What is up with that?