VS2008, IIS7, Windows Server 2008 and the Bleeding Edge

Last post 04-10-2008 9:37 PM by MrBruce. 5 replies.

Page 1 of 1 (6 items)
	Sort Posts: Previous Next

04-07-2008 6:16 PM

sokmonkey67
Joined on 02-11-2008
Posts 4

VS2008, IIS7, Windows Server 2008 and the Bleeding Edge

Reply Contact

I, like many of you out there I'm sure, am starting to work with v3.0 RC1 in the new VS world. I wanted to open up a discussion surrounding getting dashCommerce up and running in VS2008 on Vista, AJAX and deployment to an IIS7/Win2k8 environment. My initial challenge is surrounding a configuration error, which I am sure is somewhat familiar:

************************************************************

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 37:     <compilation debug="true">
Line 38:       <assemblies>
Line 39:         <add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
Line 40:         <!--<add assembly="System.Web.Extensions, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>-->
Line 41:         <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

Source File: E:\web\woodburytec\htdocs\Lenses\web.config Line: 39

Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Version Information: Microsoft .NET Framework Version:2.0.50727.1434; ASP.NET Version:2.0.50727.1434

*********************************************************

I have seen various ideas as to why this error is occurring, however what I do know is that it does not necessarily have to do with AJAX being installed in the environment. Has anyone dealt with this issue? Any ideas would be helpful...I will also update this thread as I gain more info/insight...

Thanks!

Filed under: General, dashCommerce 3 RC1, Visual Studio 2008, IIS7, Windows Server 2008, AJAX

04-07-2008 6:22 PM In reply to

sokmonkey67
Joined on 02-11-2008
Posts 4

Re: VS2008, IIS7, Windows Server 2008 and the Bleeding Edge

Reply Contact

Oh, and one note on the error--I was playing around with entries reflecting different System.Web.Extensions versions...I am not sure if the line commented out reflects a valid version or not...I know 3.5.0.0 exists...any thoughts?

04-07-2008 9:07 PM In reply to

yitzchok
Joined on 02-11-2008
New York
Posts 476

Re: VS2008, IIS7, Windows Server 2008 and the Bleeding Edge

Reply Contact

I think the best way find out what to put into the configuration file to change to AspNet AJAX 3.5 is to create a new web project in VS2008 and look what it does for you

Find a bug? Create a Work Item for a fast response.. Want to help? Create a patch for us!

04-09-2008 9:32 PM In reply to

sokmonkey67
Joined on 02-11-2008
Posts 4

Re: VS2008, IIS7, Windows Server 2008 and the Bleeding Edge

Reply Contact

OK...so here's what I have found out...due to the fact that my hosting provider does not support AJAX 1.0 on their Win2k8, so System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" needed to be updated to reflect Version=3.5.0.0...this also includes the entry for System.Web.Extensions.Design...

So, at this point I am interested in finding out how people are opening dashCommerce 3.0 RC1 in VS2008. Any suggestions, experiences, lessons, etc...?

04-10-2008 8:34 PM In reply to

yocuteem
Joined on 03-17-2008
Philadelphia Area
Posts 64

Re: VS2008, IIS7, Windows Server 2008 and the Bleeding Edge

Reply Contact

I ran into that problem in the beta, and fixed it the same way, just upgraded to AJAX 3.5 and that fixed it. I am developing a site using DC 3.0 in VS 2008.

Tim

04-10-2008 9:37 PM In reply to

MrBruce
Joined on 02-11-2008
Juno Beach, FL
Posts 120

Re: VS2008, IIS7, Windows Server 2008 and the Bleeding Edge

Reply Contact

sokmonkey67:

OK...so here's what I have found out...due to the fact that my hosting provider does not support AJAX 1.0 on their Win2k8, so System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" needed to be updated to reflect Version=3.5.0.0...this also includes the entry for System.Web.Extensions.Design...
So, at this point I am interested in finding out how people are opening dashCommerce 3.0 RC1 in VS2008. Any suggestions, experiences, lessons, etc...?

My host is very cutting-edge. I simply asked him to install the requisite "stuff" and he did!

All I did was open the .SLN file in VS2008, choosing to upgrade it to the VS2008 format and ASP.NET 3.5, then Build Solution. Then I zipped the contents of the WEB directory, uploaded that to my host and unzipped it there. Then in the browser, I ran the install/install.aspx file - worked beautifully!

If you have any other questions, I'd be pleased to try to assist!

--
Bruce

Page 1 of 1 (6 items)