Permalink
Browse files

Setting up initial ReSharper VS debugging options

  • Loading branch information...
1 parent 1a60d81 commit 6b10bdc8da77ec361a16eec6c0a525da13367911 @agross committed Oct 27, 2012
@@ -47,11 +47,16 @@
</ItemGroup>
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<Import Project="$(SolutionDir)\.nuget\nuget.targets" />
- <!-- To modify your build process, add your task inside one of the targets below and uncomment it.
+ <!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.Common.targets.
<Target Name="BeforeBuild">
</Target>
<Target Name="AfterBuild">
</Target>
-->
-</Project>
+ <PropertyGroup>
+ <StartAction>Program</StartAction>
+ <StartProgram>$(DevEnvDir)devenv.exe</StartProgram>
+ <StartArguments>/rootsuffix mspec /ReSharper.Internal /ReSharper.Plugin "$(SolutionDir)\Build\Debug\Machine.Specifications.ReSharperRunner.7.1.dll"</StartArguments>
+ </PropertyGroup>
+</Project>
View
@@ -14,6 +14,6 @@ in the debugged Visual Studio instance.
Visual Studio will choose the debugger based on the framework version the plugin is compiled against. This why we need
a debugger project for each version of Visual Studio ReSharper supports. To debug the plugin for
-- ReSharper on VS 2010, use Machine.Specifications.ReSharperRunner.Debug.VS2010
+- ReSharper on VS 2010/2012, use Machine.Specifications.ReSharperRunner.Debug.VS2010
- ReSharper on VS 2008, *transiently* switch the Machine.Specifications.ReSharperRunner.Debug.VS2010 to be compiled
against .NET 3.5 (or create a new debugger project for .NET Framework 3.5).

0 comments on commit 6b10bdc

Please sign in to comment.