Right after I set options in "Server Configuration", I have tried to run " Monday, November 28, PM. Hi Mark, I have no idea why the server says the file is not found. I'm thinking the asp. I'm not sure what WSS does. You can also try running filemon from sysinternals. NET 1. What do you suggest to check with FileMon? Thanks, Mark. Tuesday, November 29, AM. NET 2. Can you access other web services on the machine when WSS is allowed?
I'd try creating a small service to verify this. If WSS has an extension, too, you can also try disabling it and see if it changes anything. With filemon I was thinking to monitor file accesses from w3wp.
You can also look in IIS logfiles and see if beside the http error you get more information from the Windows error code sc-winstatus Alin. Tuesday, November 29, PM. Hi Mark, If you try to browse the service with InternetExplorer do you get a warning dialog?
I'd expect a warning message that tells the certificate is invalid for some reason. You mention a " standard certificate dialog" - see if this dialog provides more info about what's wrong with the certificate. If the problem is that your certificate is issued by an untrusted certificate authority you can probably solve the problem by installing the certificate on the client as described in the document.
Under this subkey, the registry entry ProviderRegKey is set to a string that represents the subkey that you placed in the registry in step 1. Your source control plug-in will use the same subkey and entry names, but the value will be different. The name of this entry is the user-readable name of the provider the same as the value specified for the SCCServerName entry , and the value is, once again, the subkey created in step 1.
There can be multiple source control plug-ins registered in this way. The value of this entry points to another subkey. Each entry has a name and a value. The IDE displays a list of these names to the user. When the user chooses a name, the IDE finds the value for the selected name that points to a subkey. A source control plug-in needs to support both ways of finding the DLL and, consequently, sets ProviderRegKey , overwriting any previous setting.
More importantly, it must add itself to the list of InstalledSccProviders so the user can have a choice of which source control plug-in to use. Create a File System or local IIS Web project use Browse button to point to the project's location; the path determines what type of Web project is created. Create a Remote Site Web project. Solution was added to source control. Remote Site project is NOT under source control.
Remote Site projects must be controlled from their own IIS server. Create a single project solution. If this step succeeds, continue to next step. Click Yes to add the project to the same location. Result from Step 2: The project and all files within the project have a checked out source control indicator, and a ToolTip displays "Not under source control".
Result from Step 5: Project and solution file are in the same folder in source control. Attempt to add project and solution to source control. Cancel after you are in source control system. Thanks for your reply. I have read quite a few tutorials the link you posted is not working , and as per one msdn article you do have to make the com visible and you also have to check the box in your build configuration to Register interop.
However, when you do both of them it fails to build and throws a build error. But if you make comvisible false and check register interop, it builds fine. And I have actually managed to make it work. I assigned a signed key to the project and then registered the dll.
Although it gave the same dll Error 'DLL was loaded but entry point was not found' but when i started the visual sourcesafe the add-in was working. I still dont know why it throws the dll error. Also i had to manually enter a key in to the registry otherwise it would not work.
0コメント