Error 404 means file not found, but when you access an ASP.NET page like default.aspx and your double checked its existence, all this doesn’t make sense. The next thing to look into is the DLL assemblies referenced by the web application. In many case the DLL is not copied into the server either in the bin folder or the General Assembly Cache
Products such as RavenDB which includes an option to deploy it as a IIS web service, however it has dependency on non core .NET Framework assemblies such as in my case Microsoft.Web.Infrastructure.
If you do a clean install of IIS on Windows Server and try to deploy RavenDB, you will encounter a Microsoft.Web.Infrastructure.dll not found error.
To fix this just download the Web Platform Installer (http://microsoft.com/web) on your Windows Server and install the ASP.NET Web Pages component on your Windows Server
Today I am trying out JQuery on Visual Studio 2008 for the first time. I go to the website at www.jquery.com and downloaded the library as well as the document for Visual Studio.
So I imported the JQuery library into my VS project
But when I want to try to the intellisense, I notice it is not working!! It should be able to recognize the famous $!!
Then I realize at the bottom of the VS IDE, there is an error message –
Warning 1 Error updating JScript IntelliSense: D:\workspace\Projects\JQuerySample\JQuerySample\scripts\jquery-1.3.2.js: Object doesn’t support this property or method @ 2139:1 D:\workspace\Projects\JQuerySample\JQuerySample\Default.aspx 1 1 JQuerySample
But this is not a bug inside the JQuery library itself. So I went back to scottgu’s blog post about on JQuery I notice something very difference with his library (besides the fact that he is using version 1.2.6).
That vsdoc2 is the cause of the problem here! Just rename it to jquery-1.3.2-vsdoc.js and you got JQuery Intellisense working!
Go here to download the files
Just realize one problem with LINQ to SQL
Unable to serialize the session state. In ‘StateServer’ and ‘SQLServer’ mode, ASP.NET will serialize the session state objects, and as a result non-serializable objects or MarshalByRef objects are not permitted. The same restriction applies if similar serialization is done by the custom session state store in ‘Custom’ mode.
When you have your ASP.NET session state stored in SQL Server, when you put any instance of your LINQ to SQL object into the session, you will hit by the about stated error.
I am still working on a fix for this. Will post the solution here once I found it.