How do I force localhost to see a project? 1

[OhioSteve]

I have been given custody of an existing asp.net application. The previous developer published from his localhost to the production server. I physically went onto his localhost and burned the project onto a cd. Then I put the project onto my localhost.

I tried several times to work with this project. But all of my attempts failed. I can give you a detailed account of my attempts. But the bottom line is, I need to know how to get my VS installation and my IIS to interact with this project.

 

[dvannoy]

Did you create a virtual directory? You need to create a virtual directory for that project. Also, the project should be under c:\inetpub\

http://wwwroot\

folder. create a virtual directory and point it to the project folder.

hope this helps

 

[OhioSteve]

Your suggestion more-or-less solved the problem. I had always created the virtual directory before starting a project. I had not considered creating the virtual directory AFTER the project. Of course, this is a special situation, because I am inheriting a completed project.

After I made the directory, I opened the project and I got this message:

"The solution appears to be under source control, but its binding information cannot be found. It is possible that the MSSCCPRJ.SCC file or another item that holds the source control settings for the solution, has been deleted. Because it is not possible to recover this missing information automatically, the projects whose bindings are missing will be treated as not under source control."

I did not understand the message, so I ignored it. The project seemed to work okay. I am starting detailed tests now.

 

[jbenson001]

I think to avoid the error messages, just remove any vss files in the project. I belive they are .vss. If they are not in the project, then you should not receive the error.

Jim

 

[ca8msm]

There are qquite a few posts about this when one party doesn't have a copy of source safe. The instructions I keep handy for ths situation are:

1. Delete all the "<projectName>.vbproj.vspscc" project MetaData files. C# developers should look for the files named "<projectName>.csproj.vspscc"

2. Delete all the "vssver.scc" files (if any).

3. Delete the "<solutionName>.vssscc" file.

4. Open the "<solution>.sln" file in a text editor (such as notepad.exe) and
remove all the information between the following two "Section start/end
identifiers" (including the identifiers):
GlobalSection(SourceCodeControl)
....
EndGlobalSection

5. Open each "<projectName>.vbproj"file (or "<projectName>.csproj"-file
for c# developers) in a notepad.exe style editor. Remove all entries similar to the ones below.
SccProjectName = ...
SccLocalPath = ...
SccAuxPath = ...
SccProvider = ...


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[OhioSteve]

Yeah, you guys are right. The previous programmer had stored his stuff in source safe. Another coworker had "checked it out" for me. But have I learned that that is not sufficient. You must edit/delete some files to stop it from whining about SS. I followed these instructions, and they worked for me:









1. Delete the following files from your solution or project folder and any project folders in this folder: *.scc, * .vspscc, and .vssscc.

2. Select all remaining files and folders in the solution or project folder, and remove the read-only attribute from the selected files and folders. VSS uses the read-only attribute for items that are checked in, so you need to remove this attribute before editing any files. Keep in mind that some projects may be located outside the parent solution folder. This is nearly always true for Web projects, which are usually located in the Inetpub\

http://wwwroot

folder.

3. If you want to remove a solution file from VSS source control, edit the solution file (.sln) in a plain text editor like Notepad. Remove the SourceCodeControl GlobalSection section. Remove from and including this line: “GlobalSection(SourceCodeControl) = preSolution” to and including this line: “EndGlobalSection”

4. Edit any project files (.vbproj or .csproj) in a plain text editor. Remove these four lines, which are located at the top of the project file in either the Visual Basic or CSHARP node: SccProjectName = "SAK", SccLocalPath = "SAK", SccAuxPath = "SAK", SccProvider = "SAK".

5. If you have enterprise template project files (.etp), they also must be edited, remove the SourceControlSettings node including content, from the start tag<SourceControlSettings> to the end tag </SourceControlSettings>.That's all you need to do. Your solution and project are now fully removed from VSS source control.