Missing Microsoft.Web.Infrastructure
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
Error updating JScript IntelliSense: Object doesn’t support this property or method @ 2139:1
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).

I notice mine has got an extra number 2 at the end of vsdoc there. So I go back to the Google code side where I downloaded the file and I found out en they release a new vsdoc file to replace the exisiting deplecated one, they ‘tangan gatal’ change the name to jquery-1.3.2-vsdoc2.js. VS Interllisense only programmed to regconized [Javascript file name]-vsdoc.js without the 2 at the back there.
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!
Slides and documents on Devtalk 10 Apr 09
Go here to download the files
LINQ to SQL and SQL Server Session State – Unable to serialize the session state
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.
SQL Server named pipes error has nothing to do with the pipe
I got a ASP.NET project with a integrated SQL Express database in to App_data folder like below
When I click on F5 into debug mode and I try out some database operation, I got hit by the following error message.
Connection Error: (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.
Peek into SQL Server Configuration Manager and I see that Named Pipes is enable
So what is wrong with it? My network is OK
After searching the web I realized that SQL Server Agent service got disabled and it can cause problem with database in App_data folder. Open up the Services MMC and confirmed this.
So I enabled the SQL Server Agent service and got it started and my ASP.NET can functions per normal.
No guarantee it will work for your scenario though.
