I found some information about http://www.whitehouse.gov/ web site and it turns out that this site runs on ASP.NET. Some interesting characteristics:
- web server is IIS 6.0
- ASP.NET version is 2.0.50727
- they use jQuery 1.2.6 but jQuery scripts are not hosted in Google global script hosting service,
- pages are GZIP compressed and they seem to use pretty high compression level
- JPG files are highly compressed to make page load faster.
Further details on website code --> http://dotnetperls.com/Content/whitehouse-gov-Site.aspx
Friday, January 23, 2009
Tuesday, January 20, 2009
You can use .NET 3.5 with Visual Studio 2005
Myth and Misconceptions
It seems that the recent release of Visual Studio 2008 and .NET framework 3.5 is causing lots of confusion. The .NET framework does not have any built-in dependency on Visual Studio. NET 3.5 continues to exploit version 2.0 of the CLR. Visual Studio 2005 is perfectly happy to compile your code against .NET 3.5 assemblies. They are just assemblies. Most of the assemblies in .NET 3.5 are identical to those in .NET 3.0. There are some new assemblies with new features.
The wonderful new LinQ technologies introduced in .Net 3.5 rely on explicit compiler-level support, and therefore require LinQ aware compilers in Visual Studio. The new version of Visual Studio i.e. VS 2008 provides these compilers, allowing developers to take advantage of the new monadic syntax. In addition, Visual Studio 2008 has several new features designed to make it easier to exploit NET 3.5 features such as Ajax and the foundation libraries (WCF, WF and WPF).
Thus .NET 3.5 is perfectly suitable to run on VS 2005 as well. Microsoft has long since split the versioning of the framework from the versioning of the run-time environment.
Why is this explanaition on versioning important?
Well, not everyone is ready to upgrade to Visual Studio 2008. Ofcourse the expense involved in upgrading is a point of decision. Apart from that people dont fall into misconception of various versioning dependencies with the IDE's which is not the case here.
What are the issues if we use .NET 3.5 with VS 2005 ?
Visual Studio 2005 does not have access to various new project and file templates and tools that support the new version of the framework. Developers may need to do more coding in Visual Studio 2005 than would be necessary in Visual Studio 2008.
How to access improvements in .NET 3.5 using VS 2005
As an example, consider the new integration between WF and WCF, provided in the new System.WorkflowServices assembly. The integration is provided via the new WorkflowServiceHost class and a couple of new activities. Visual Studio 2008 has new template support for building workflow services, and comes with a very useful new WCF test harness. However, exploiting this new functionality in Visual Studio 2005 is trivial. Create a WF workflow library, add a reference to System.WorkflowServices and add the new activities to your tool box. Finally, use the WCF Service template to add a service class to your project and you are just about in the same position as you would be in Visual Studio 2008 if you used the new Workflow Service project template. You'll need to write a couple of lines of code to use WorkflowServiceHost to host your service, of course.
It seems that the recent release of Visual Studio 2008 and .NET framework 3.5 is causing lots of confusion. The .NET framework does not have any built-in dependency on Visual Studio. NET 3.5 continues to exploit version 2.0 of the CLR. Visual Studio 2005 is perfectly happy to compile your code against .NET 3.5 assemblies. They are just assemblies. Most of the assemblies in .NET 3.5 are identical to those in .NET 3.0. There are some new assemblies with new features.
The wonderful new LinQ technologies introduced in .Net 3.5 rely on explicit compiler-level support, and therefore require LinQ aware compilers in Visual Studio. The new version of Visual Studio i.e. VS 2008 provides these compilers, allowing developers to take advantage of the new monadic syntax. In addition, Visual Studio 2008 has several new features designed to make it easier to exploit NET 3.5 features such as Ajax and the foundation libraries (WCF, WF and WPF).
Thus .NET 3.5 is perfectly suitable to run on VS 2005 as well. Microsoft has long since split the versioning of the framework from the versioning of the run-time environment.
Why is this explanaition on versioning important?
Well, not everyone is ready to upgrade to Visual Studio 2008. Ofcourse the expense involved in upgrading is a point of decision. Apart from that people dont fall into misconception of various versioning dependencies with the IDE's which is not the case here.
What are the issues if we use .NET 3.5 with VS 2005 ?
Visual Studio 2005 does not have access to various new project and file templates and tools that support the new version of the framework. Developers may need to do more coding in Visual Studio 2005 than would be necessary in Visual Studio 2008.
How to access improvements in .NET 3.5 using VS 2005
As an example, consider the new integration between WF and WCF, provided in the new System.WorkflowServices assembly. The integration is provided via the new WorkflowServiceHost class and a couple of new activities. Visual Studio 2008 has new template support for building workflow services, and comes with a very useful new WCF test harness. However, exploiting this new functionality in Visual Studio 2005 is trivial. Create a WF workflow library, add a reference to System.WorkflowServices and add the new activities to your tool box. Finally, use the WCF Service template to add a service class to your project and you are just about in the same position as you would be in Visual Studio 2008 if you used the new Workflow Service project template. You'll need to write a couple of lines of code to use WorkflowServiceHost to host your service, of course.
Subscribe to:
Posts (Atom)