Getting Not Implemented Error

cwarford · Post by **cwarford** » Tue Oct 17, 2006 11:57 am

I am getting a "Not Implemented" error when trying to open an ASP.NET Web Project/Solution in Microsoft Visual Studio .NET 2003. We are using Vault Version 3.1.7 (3719).

I am trying to add the solution to source control through Microsoft Visual Studio .NET 2003. However, the solution and project files have already been added to Vault directly through the Vault Client Tool. I wish to add them through Visual Studio so that the projects/solutions get binded to Vault and I am able to Get Latest/Check In/Check Out the source code from Visual Studio instead of through Vault.

The projects and solutions seem to add to source control fine through Visual Studio but when I go to open them again I get the Not Implemented error. To open the solution I simply go to the file menu in Visual Studio and click Open Solution.

Any thoughts or ideas as to why I am getting this error?

Thanks in advance,
Corey

lbauer · Post by **lbauer** » Tue Oct 17, 2006 5:09 pm

I don't think we've seen that error before. It might be a binding problem, but it could be something else.

The proper bindings are not created when you add files to or get files from Vault with the Vault GUI Client.

The recommended way is to add the solution or project to Vault via Visual Studio. To add a project, select File->Source Control->Add Solution to Source Control. This will create the proper bindings on the machine for the user adding the project.

Then, other users should retrieve the project with Visual Studio by using the File->Source Control->Open Solution from Source Control.

For those projects already in Vault that are getting binding errors, you might also be able to fix the bindings by using the Change Source Control command. Open the project in Visual Studio, then select Change Source Control and unbind, then rebind the project.

If the project is successfully bound, other users should backup their working directories and do a fresh Open from Source Control.

For more information about using Vault and Visual Studio, see this KB article.
http://support.sourcegear.com/viewtopic.php?t=776

If it's not a binding issue, then perhaps it has something to do with the type of project you have.

Here's a thread from a Microsoft forum by a user who was getting the same type of error. Is any of this relevant to your situation?
http://groups.google.com/group/microsof ... ebd4582a7a

cwarford · Post by **cwarford** » Wed Oct 18, 2006 5:19 am

I tried to the un-bind/re-bind source control but it does not seem to be working.

It looks like the product we are using could possibly be the issue. We are using a product from ASNA called AVR.NET and since it requires different add-ins for the Visual Studio and the .NET framework this could be why it will not bind the projects and solutions correctly unless they are done through Visual Studio.

I am going to try a few other things and if any of them work I will post them here for future reference.

lbauer · Post by **lbauer** » Wed Oct 18, 2006 7:46 am

Thanks for the information. In my research, I found that add-ins were usually the culprit in "Not Implemented" errors from Visual Studio.

cwarford · Post by **cwarford** » Wed Oct 18, 2006 8:24 am

This worked for us. It allowed us to add the solution/project to Vault through Visual Studio so that the bindings were setup properly and we could check-in, check-out, get latest version from Visual Studio.

Before trying to add solution and project to source control through Visual Studio, take a copy of solution/project to local machine and take read-only access off entire directory. Then remove the following from the vrproj file using notepad.

SccProjectName = ""
SccLocalPath = "."
SccAuxPath = ""
SccProvider = ""

The Scc* references may or may not contain values but remove them anyway.

Remove the file(s):
*.vrproj.vspscc (this would be vbproj for VB.NET users)
*.vssscc
*.SCC

In Visual Studio, right-click on the solution name and click add solution to source control, if a message appears, click continue.

To get solutions to work under source control remove the following line from SLN file (using a text editior like notepad) after you have added the solution/project to source control through Visual Studio:

SccProjectEnlistmentChoice1 = 2

This can be done using notepad directly though the vault client tool. Once the sln file has been edited, check it back in through Vault.

lbauer · Post by **lbauer** » Wed Oct 18, 2006 9:27 am

Thanks for the details. This can help other users who might encounter this issue.