Dave Burke : Freelance .NET Web Developer specializing in Online Communities

CS Nuglet: Resolving the SDK VS2005 debug invalid syntax error

I updated a Community Server 2.1 site SDK to SP2 the other day and when firing up the debugger in Visual Studio 2005 I received the following message, "Unable to start debugging on the web server.  The debug request could not be processed by the server due to invalid syntax."


Microsoft has a good MSDN article on this with one of the things to check is to run the app in Visual Studio without debugging using "Start without Debugging."  When I did I realized the url was http://localhost/cs.  This is CS's default project url, but not of the site I just upgraded to the SP2.  My site's url was http://cs21demo.

I'll get straight to the fix.  The SDK's web .CSPROJ file's IISUrl default setting is http://localhost/cs.  To change this setting and debug your Community Server Web Application you'll need to update the Web Application's Startup Project Url with Properties->Web tab as shown below.  Once that is done, you can press F5 and step through the inner beauty of Community Server at your leisure.

 

Comments (3) | Post RSS RSS comment feed

Posted on 12/25/2006 7:54:00 PM by Dave Burke
Categories: Community Server
Tags: no tags for this post

Related posts

Comments (3) -

12/27/2006 1:22:34 AM Permalink

Ummm Dave,

You can use "EXEC cs_system_AddNewUrl OriginalUrl, NewUrl" to add the "localhost/cs" URL to your site.

Don't worry, I won't tell anyone.  Smile

Bill Bosacker |

12/27/2006 2:30:51 AM Permalink

Hey, Bill!  I never should have been on your case to start blogging! Smile  The site ran fine when I loaded it in a browser, so it wasn't a cs_site issue.  It was the DEBUGGING startup IISUrl in the .csproj file that needed updating so that VS2005 would launch in debug mode.  VS2005 never got to the web.config settings, which I purposely mucked up to see if it had an effect, which it didn't.  

So otherwise, that was a good tip.  You probably shouldn't tell anyone for this particular issue though.  Great hearing from you, man!

daveburke |

12/27/2006 5:27:35 PM Permalink

That's weird.  I just rebuilt my workstation and I am debugging the site under localhost/cs without any issues.  I did learn one thing a couple weeks ago when I rebuilt my domain (had been having issues for a couple years as it originated from an ald NT 3.51 domain) and that is that you need to make sure that whatever account the pool runs under, must have full rights to the TEMP directory and special rights to the .NET temp folder as well.  By default, the SERVICE accounts don't have rights and thus fail to function.

Anywho, we'll see how the new position works out for ya.  Take it easy...

Bill Bosacker |


Powered by BlogEngine.NET 2.0.0.36
Theme by Dave Burke