Checkout problems with WebApplications

droyad · Post by **droyad** » Thu Apr 03, 2008 6:49 pm

Vault Advanced Client 4.1.1
Value Server 4.1.1
Visual Studio 2008 RTM

We have just recently upgraded to 4.x, and I have noticed a problem with WebApplications.

On Web Projects with "Edit and Continue" turned on, you can edit the .aspx files when running in debug mode, and edit .cs files when debugging is paused.

However Vault does not check out the files when they are edited or saved while the VS is in debug mode. If debugging is stopped, the files are still not checked out, which leads to them being "Renegade". Nothing appears in the Pending Checkins.

Also the SCC icons (ie the lock) usually dissapear on some, then all of the items in the Solution Explorer.

None of this occurs on projects other than WebApplications, even if they are in the same solution.

Any ideas what could be going on? Vault is configured in "VSS" mode.

ian_sg · Post by **ian_sg** » Fri Apr 04, 2008 2:21 pm

We're trying to reproduce this behavior. Are you talking about a web application project, or a web site project?

A web application has a project file (csproj or vbproj). A web site project does not; it just has a folder. (So you can identify it in the solution explorer because its name is a path with a trailing slash.)

ian_sg · Post by **ian_sg** » Fri Apr 04, 2008 2:31 pm

Also, are you debugging with the built-in Visual Studio web server, or IIS?

droyad · Post by **droyad** » Fri Apr 04, 2008 6:22 pm

It is a WebApplication with a project file. We are using the VS web server.

ian_sg · Post by **ian_sg** » Mon Apr 07, 2008 9:03 am

We've been unable to reproduce this.

Does it happen for every developer? Does it happen every time, or only intermittently? Do you have other web application projects? Do you see this problem on them, as well?

droyad · Post by **droyad** » Mon Apr 07, 2008 7:51 pm

Ok, tried to reproduce it on a new project, but I could not do it repeatedly. It looks like the problem occurs if the WebApplication is renamed first from within VS, removed from the App, the folder renamed in Vault, then readded to the solution.

However I could not reproduce it every time. But is definitely only occurs with edit-continue enabled.

I think it may be to do with the SCCProject name in the .csproj file. How can I determine the correct value for that?

ian_sg · Post by **ian_sg** » Wed Apr 09, 2008 12:00 pm

You shouldn't ever have to manually change the SccProject name in the project file.

We'll do some testing with the steps you've described and see if that reveals a problem.

droyad · Post by **droyad** » Wed Apr 09, 2008 7:31 pm

Attached are some files showing this in action, as I know how difficult it is to debug something you don't see (sorry I couldn't get it sooner).

The video shows the solution being added to a blank (well, was previously added, but it was deleted) repository. Default.aspx being edited and the checkout occurs correctly. Solution is run, and Default.aspx is edit again, but no checkout occurs, even after a save.

After this is done, the Vault client shows the file (correctly) as 'Renegade', and a Get Latest within VS shows this as well.

As mentioned previously if I create a new project this does not occur, until some time later. This occured in MyWeb, which I then Unbound, cleared the repository and then (in the video) rebound.

Hope this helps,

Rob

ian_sg · Post by **ian_sg** » Thu Apr 10, 2008 1:00 pm

Thanks for the detailed report Rob. I was able to figure out exactly what's happening. If you want the short answer, and a work-around, it's this:

In the web application project properties, on the "Web" tab, change the port back to the default, "Auto-assign Port".

A more detailed explanation:

The bug only shows itself when a specific port is assigned here, which isn't the default, which is why we couldn't reproduce it on any old project.

This is one of those gray-area bugs where it seems like Visual Studio is doing the wrong thing, but we'll probably have to figure out a work-around. When the debugger is running on a web application project and a specific port is being used by the VS development server, the project returns an error when we ask it if it owns a file. The error returned is "Unable to launch the ASP.NET Development Server because port 'x' is in use." I'm not sure why it's trying to launch the server, or claiming to, but that's what's happening.

I'll log a bug. In the mean time, the workaround is to stick with the default auto-assigned port. Another alternative is to use IIS rather than the VS development server for debugging.

Sorry for the inconvenience.

art · Post by **art** » Wed Dec 03, 2008 8:24 am

Hi
I'm currently dealing with the same issue without having a solution.
Did you resolve the problem ? In case of yes, please, could you send me an email to artcarrion@yahoo.com.ar with the solution ?
Thanks in advance.

Art.

ian_sg · Post by **ian_sg** » Wed Dec 03, 2008 8:35 am

We haven't determined the fix for this issue. The workarounds I listed are still the best option.

SourceGear Support