Forums » Community Server Archive (read only) » Coding with Community Server » Visual Studio 2008

Visual Studio 2008

rated by 0 users
This post has 13 Replies | 5 Followers

dagaci
Not Ranked
Posts 21
Points 405
Reply |Contact
By: dagaci
Posted: Tue, Nov 27 2007 8:25 AM

Has anyone tried opening the Communityserver SDK 2007.1 project (http://get.communityserver.org/download/survey.aspx?sku=cssdk) in the new Visual Studio 2008. I've tried opening it and it fails when trying to open the web project. If anyone can help with that then that would be great.

Update 2007-11-29: On Vista you need all the IIS6 compatibility options installed. I resolved the problem by opening the original web project file in VS2005, then changing WebProject options to use the VS2005 Internal web server instead of IIS. Reopeining the project and converting with VS2008, with "Run as Administratror" then succeeded. 

 
tibor
Not Ranked
Posts 12
Points 210
Reply |Contact
By: tibor
Posted: Wed, Nov 28 2007 1:28 AM In reply to

I have same issue.

 
  • Post Points: 20 |
Scott Watermasysk
Top 25 Contributor
Posts 2,227
Points 44,405
CS Developers
Reply |Contact
By: Scott Watermasysk
Posted: Wed, Nov 28 2007 1:41 AM In reply to

We have not done a lot of testing in VS 2008. So far what we have found is converting projects likely requires Admin access. Are you using Vista? Or a locked down XP? Could you try opening the solution as an admin?

Thanks,
Scott

Follow Me On Twitter Simpable
 
  • Post Points: 20 |
tibor
Not Ranked
Posts 12
Points 210
Reply |Contact
By: tibor
Posted: Wed, Nov 28 2007 2:07 AM In reply to

I'm using english Vista Enterprise 32. Visual studio is started with admin rights (Run as Administrator) and I receive System.Runtime. InteropServices.COMException during project conversion.

I will try it on XP computer later today.

 
  • Post Points: 20 |
Thomas Freudenberg
Top 200 Contributor
Posts 129
Points 5,510
MVPs
Reply |Contact
By: Thomas Freudenberg
Posted: Wed, Nov 28 2007 2:21 PM In reply to

You have to install IIS Metabase and IIS 6 configuration compatibility. That´s required by VS2K8 to talk to IIS.

Regards, Thomas

Thomas Freudenberg

 
zahi
Not Ranked
Posts 1
Points 20
Reply |Contact
By: zahi
Posted: Wed, Nov 28 2007 4:51 PM In reply to

Hi. The same problem IIS Metabase and IIS 6 configuration compatibility are installed. but still the same problem. what to do? please help. thanks zahi.

 
  • Post Points: 20 |
Thomas Freudenberg
Top 200 Contributor
Posts 129
Points 5,510
MVPs
Reply |Contact
By: Thomas Freudenberg
Posted: Wed, Nov 28 2007 5:27 PM In reply to

For me it helped just to install IIS Metabase and IIS 6 configuration compatibility and start VS2K8 elevated.

Regards, Thomas

Thomas Freudenberg

 
  • Post Points: 20 |
tibor
Not Ranked
Posts 12
Points 210
Reply |Contact
By: tibor
Posted: Thu, Nov 29 2007 4:28 AM In reply to

Unfortunately it does not work for me. I tried to convert it on both Vista and XP, but without success.

 

EDIT: I managed to solve my issue. I have to edit Web\CommunityServerWeb20 (Internal).csproj file. I replaced

          <IISUrl>http://cs2007</IISUrl>

with

          <IISUrl>http://localhost/cs</IISUrl>

 
  • Post Points: 35 |
shakes
Top 75 Contributor
Posts 308
Points 4,675
Reply |Contact
By: shakes
Posted: Thu, Dec 13 2007 10:28 PM In reply to

I am trying to get vs2008 up and running so i can do some dev work on my cs site and have run into a few problems with when i build. What do i need to do to test a cs site? I am getting the error below and am not sure what to do. Also will i need to set up a database for the uncompiled test site?...I already have a full compiled site running at localhost that has quite a few UI changes...I have both running under "Default Website" not sure if i should create another website or if this setup works. Oh well any Ideas much appreciation!

Side Note: the basic theme seems to have errors when the upgrade wizard runs.  

Server Error in Application "Default Web Site/virgincs"

HTTP Error 500.0 - Internal Server Error

Description: This application is running in an application pool that uses the Integrated .NET mode. This is the preferred mode for running ASP.NET applications on the current and future version of IIS.

In this mode, the application should not specify ASP.NET module components in the <system.web>/<httpModules> configuration section. Instead, it should use the <system.webServer>/<modules> configuration section to load ASP.NET module components. You have the following options:

1) Migrate the application to work with the Integrated .NET mode (PREFERRED).

You can migrate the application configuration, including the contents of the <httpModules> configuration section, by using the following from a command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "Default Web Site/virgincs"

After you migrate your application, it will run in both Classic and Integrated .NET modes, as well as on downlevel platforms.

2) Move this application to an application pool using the Classic .NET mode.

You can move the application to the default application pool using the Classic .NET mode by running the following from an command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE set app "Default Web Site/virgincs" /applicationPool:"Classic .NET AppPool"

Alternatively, you can use any other application pool on your system that is running in the Classic .NET mode. You can also use the IIS Administration tool to move this application to another application pool.

It is preferred that you migrate this application by using option 1 to take advantage of the benefits provided by the Integrated .NET mode.

Error Code: 0x80070032

Notification: BeginRequest

Module: ConfigurationValidationModule

Requested URL: http://localhost:80/virgincs/

Physical Path: C:\WebSites\VirginCS_3.1.20917.1142.sdk\source\Web\

Logon User: Not yet determined

Logon Method: Not yet determined

Handler: StaticFile

Most likely causes:

  • IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
  • IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
  • IIS was not able to process configuration for the Web site or application.
  • The authenticated user does not have permission to use this DLL.
  • The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

What you can try:

  • Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
  • Check the event logs to see if any additional information was logged.
  • Verify the permissions for the DLL.
  • Install the .NET Extensibility feature if the request is mapped to a managed handler.
  • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

More Information... This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.

Microsoft Knowledge Base Articles:

  • 294807
Server Version Information: Internet Information Services 7.0.

peace shakes

Carolina Pulse

 
  • Post Points: 5 |
shakes
Top 75 Contributor
Posts 308
Points 4,675
Reply |Contact
By: shakes
Posted: Mon, Dec 17 2007 10:19 PM In reply to

never mind i think i have it all figured out... 

peace shakes

Carolina Pulse

 
  • Post Points: 20 |
Marc Mezzacca
Top 200 Contributor
Posts 113
Points 1,700
Reply |Contact
By: Marc Mezzacca
Posted: Thu, Dec 20 2007 3:43 AM In reply to

 Any details on how you got it working / figured it out would be much appreciated!

Next Generation Shopping

 
  • Post Points: 20 |
shakes
Top 75 Contributor
Posts 308
Points 4,675
Reply |Contact
By: shakes
Posted: Thu, Dec 20 2007 10:20 AM In reply to
The Mez What problems are you having or are you just looking for a how to doc. The problem I was having above was that cs needs to be run in classic .net

peace shakes

Carolina Pulse

 
  • Post Points: 20 |
Eric Falsken
Top 100 Contributor
Posts 209
Points 3,160
Reply |Contact
By: Eric Falsken
Posted: Thu, Jan 31 2008 7:27 PM In reply to

Running VS 2008 as admin worked for me. VS2k8 wants to reconfigure IIS. You have to let it, then go back and change it to "Classic" pipeline after the upgrade.

Eric Falsken Engineer, db4objects Blog: http://www.EveryLittleThing.net/blog/ Community: developer.db4o.com Administrator
 
  • Post Points: 5 |
Marc Mezzacca
Top 200 Contributor
Posts 113
Points 1,700
Reply |Contact
By: Marc Mezzacca
Posted: Sat, Feb 16 2008 8:09 AM In reply to

Was just looking for more of a "how-to" document.  But I'll ask specific questions once I actually do the upgrade to 2008 in the coming weeks.


Next Generation Shopping

 
  • Filed under: |
  • Post Points: 5 |
Page 1 of 1 (14 items) | RSS
Powered by Community Server (Commercial Edition), by Telligent Systems

Copyright© 2008 Telligent Systems Inc. All rights reserved
CommunityServer.com  •  Telligent.com