Source Controlled FrontPage Web?

ROTRTechTeam · Post by **ROTRTechTeam** » Sat Aug 06, 2005 8:18 am

Hi,

My web developer has just begun coding a .NET (C#) project in Visual Studio 2003. He began the project without using the Vault or any source control tool at all. After 1 week and reviewing his code, I asked him to get his code checked into the vault. He used the Vault Client to add the files. He then opened Visual Studio 2003, went to File | Source Control | Open From Source Control and logged into the Vault server and the proper repository. He selected the folder in Vault that he wanted and he gave a working folder (pointing to his existing code folder). He was prompted and chose to overwrite the existing files. He is then given a message as follows:

"The project you are attempting to open is a source controlled FrontPage web and cannot be opened directly from source control. Please use Open Project from Web command instead."

When he does that he does not have checkin/checkout options on his files.

What is going on and how do we fix this?

Thanks!

Mike Mahony
Director of Information Technology

lbauer · Post by **lbauer** » Sun Aug 07, 2005 3:14 pm

Had he been using FrontPage or FrontPage access with this project previously? Vault only supports file share access.

Here's additional info an the two types of access:
http://msdn.microsoft.com/library/defau ... method.asp

Try changing the access method and see if that works:

http://msdn.microsoft.com/library/defau ... method.asp

If that doesn't help, your user may want to delete the project from Vault and re-add it with VS.NET, using File->SourceControl->Add Solution to Source Control. This should set the proper bindings.

See details here:

http://support.sourcegear.com/viewtopic.php?t=776

ROTRTechTeam · Post by **ROTRTechTeam** » Mon Aug 08, 2005 7:49 pm

Linda,

That got the project into source control but now the web debugging is broken. How can we get that to work again and still have the source code in the Vault?

Thanks!

Mike

lbauer · Post by **lbauer** » Tue Aug 09, 2005 8:21 am

That got the project into source control

Which one of the suggestions worked for you?

How are you doing your web debugging?

Are you debugging locally or remotely?

What error messages do you get?

ROTRTechTeam · Post by **ROTRTechTeam** » Tue Aug 09, 2005 8:29 am

Well the project was already set to file access and not FrontPage access, so we removed all files from the Vault and then used "Add solution to source control" to get them in. That is what worked.

The developer is developing and debugging everything on his local machine. He is saying that the debugging is not working at all now that his files are in the Vault.

I pulled down the entire project to my machine last night and debugging seems to work. I've put in a call to him (my developer) and will post again when he has responded with what the error is that he is getting.

Thanks again for all your help so far!

Mike

ROTRTechTeam · Post by **ROTRTechTeam** » Thu Aug 11, 2005 4:44 pm

It turns out that the developer needed to reinstall the .NET Framework and once he did that, his problems went away.

Thanks again for your help!

Mike

ROTRTechTeam · Post by **ROTRTechTeam** » Tue Aug 16, 2005 5:10 am

OK, well it turns out there is still a problem. If the developer uses the Visual Studio IDE to check out and check in files and then runs the local debugger, he ends up getting an ACL error that crashes the Visual Studio IDE. The only fix is to reinstall the .NET framework. If he uses the Vault client to do the checkin/checkout everything works.

He is using Visual Studio 2003, C# and it is a web project that is being hosted on the development machine.

Any thoughts on why this is breaking the local debugger?

Thanks!

Mike

dan · Post by **dan** » Tue Aug 16, 2005 8:47 am

What version of Vault are you using (Check the Help->Tech Support to get both client/server)?

Is the web site is being debugged against on the developers own machine, and under source control?

Also, what is the ACL error that is being reported?

We'll probably want to set up a log file so we can see if the problem is within Vault. See http://support.sourcegear.com/viewtopic.php?t=2898 for how to set it up.