Hi! Thanks for your interest in VisualSVN!
It's a known problem and Blend, seemingly, is the reason of it. VisualSVN saves the global variable, named VisualSVNWorkingCopyRoot, into *.sln file after adding the project under Subversion control. Blend can't open solution files with such additional variables thought these files are quite correct. What version of the VisualSVN do you use? Please you could try the latest stabilization snapshot of VisualSVN 1.6 from http://www.visualsvn.com/visualsvn/beta/? Please tell us if the problem is fixed. Please note that this is NOT a final release and it's intended for evaluation of new features only. As workaround you could try:open your *.sln file and check if there is VisualSVNWorkingCopyRoot variable and if it is empty. If it is so, please set its value to point, i.e. change [[ GlobalSection(ExtensibilityGlobals) = postSolution VisualSVNWorkingCopyRoot = EndGlobalSection ]] to [[ GlobalSection(ExtensibilityGlobals) = postSolution VisualSVNWorkingCopyRoot = . EndGlobalSection ]] Both VisualSVN and Blend should work in this case correctly. Please don't hesitate to ask any further assistance. On Tue, Nov 18, 2008 at 9:32 PM, <[EMAIL PROTECTED]> wrote: > > *BUG Report* > > This might be a bug more on Microsoft's side but I thought I would > make you aware of it. > > Description: > > If a user adds a solution to Subversion using Visual SVN from Visual > Studio 2008 and then tries to open the solution AND/OR any of the > projects in the subfolders of the solution directory Expression Blend > will fail to open said solutions or projects. This is because of two > things. First, Visual SVN makes a modification to the .sln file adding > it's Extensibility section, normally this wouldn't cause any problems > HOWEVER when you combine it with the second issue, which is that when > Expression Blend (2.0) tries to open the .sln it fails silently. To > make matters worse apparently when Expression Blend even tries to open > a .csproj file for example in one of the subdirectories of the > solution i.e. (SolutionDirectoryName\ProjectDirectory) it has some > built mechanism to check for a .sln file in the parent directory of > the project directory thus trying to read the .sln file instead of > the .csproj and failing silently again. My fix was to not use Visual > SVN any more until this is fixed and manually add my code to my > repositories using Tortoise. This bug is especially irritating because > Blend 2 will not provide any exception information and fails > completely silently as if you never even tried to open the file. > -- Olga Dolidze VisualSVN Support
