MSDN Magazine July 2000
View Complete Post
We have an applicaiton that was converted to the new framework using the wizard in Visual Studio 2008. When we install the applicaiton in production and change the iis settings to use the 2.0 framework we start to see these errors in the event viewer on the web servers.
We are using SQL Server Session State and have 3 web servers in a load balancer.
Object reference not set to an instance of an object.</Message><StackTrace> atSystem.Web.SessionState.SessionStateModule.PollLockedSessionCallback(Objectstate
Not sure what is causing this - anyone have an ideas?
Hello, I'm updating around 15 pages from .asp to .aspx (.net 2.0)
My question is, do I have to put a header redirect 301 (permanent redirect) on each old file, or can I put it in global.asax file with a case checking for any of the 15 files?
I some tries to go to old.asp will it execute global.asax anyway?
What would the best aproach be?
We have web application migrated from Asp.Net 1.1 to 2.0. Everyhting works and runs application fine except following compilation warning. Does anybody know the solution?
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig /unsafe- /nowarn:1701,1702 /platform:AnyCPU /errorreport:prompt /warn:0 /define:DEBUG;TRACE /reference:"C:\Program Files\ComponentArt\Web.UI 2007.2 for ASP.NET 1.0\live_demos\bin\ComponentArt.Web.UI.dll" /reference:bin\DayPilot.dll /reference:
"C:\Program Files\Developer Express .NET 2005 v6.3\Sources\DevExpress.DLL\DevExpress.Data.v6.3.dll" /reference:"C:\Program Files\Developer Express .NET 2005 v6.3\Sources\DevExpress.DLL\DevExpress.Utils.v6.3.dll" /reference:"C:\Program Files\Developer Express .NET 2005 v6.3\Sources\DevExpress.DLL\DevExpress.XtraEditors.v6.3.dll" /reference:"C:\Program Files\Developer Express .NET 2005 v6.3\Sources\DevExpress.DLL\DevExpress.XtraPrinting.v6.3.dll" /reference:"C:\Program Files\Developer Express .NET 2005 v6.3\Sources\DevExpress.DLL\DevExpress.XtraReports.v6.3.dll" /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Configuration.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Data.dll /reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.DirectoryServices.dll
Windows Azure is already helping many companies move their apps into the cloud. We'll share some of the tips and tricks that we discovered working with customers on real-world migrations.
George Huey, Wade Wegner
MSDN Magazine August 2010
The CLR security model in the Microsoft .NET Framework 4 has undergone some substantial changes, including the adoption of "Level2" transparency, similar to the Silverlight security model. Mike Rousos provides an in-depth explanation of how that will likely impact authors of AllowPartiallyTrustedCallers (APTCA) libraries.
MSDN Magazine March 2010
You've probably heard that the new version of Web Services Enhancements (WSE) for the MicrosoftÃÂ® . NET Framework simplifies the process of building secure Web services. What you may not know is that most of these improvements derive from some core architectural changes made in WSE 3.
MSDN Magazine April 2006
As you move forward with your use of ADO. NET, you'll need to know how to approach situations that you previously learned to handle in ADO and now have to tackle with ADO. NET. Just as n-tiered solutions developed using Visual BasicÃÂ®, C++, and ASP often rely on ADO for their data access needs, WindowsÃÂ® Forms, Web Forms, and Web services rely on ADO.
MSDN Magazine August 2004
In recent years ADO has taken the lead as the preferred method for implementing data access in WindowsÃÂ®-based applications. Huge numbers of ADO applications are in use today and many developers are well versed in ADO development.
MSDN Magazine July 2004
MSDN Magazine May 2001
MSDN Magazine April 2001
MSDN Magazine March 2001
MSDN Magazine February 2001
A Global Positioning System (GPS) device captures lots of interesting information that can be used in many ways. This article presents a custom application built with Visual Basic that collects data from a GPS satellite and charts the course of a user relative to the satellite. Such an application is obviously well suited for use on a handheld PC and porting the original application to eMbedded Visual Basic for Windows CE is described. The differences between Visual Basic and eMbedded Visual Basic, such as support for specific control and data types, are explained. Tips for dealing with reduced screen real estate on a handheld PC, debugging, and running in an emulator are also discussed.
MSDN Magazine January 2001
MSDN Magazine September 2000