Posted by jpluimers on 2015/09/30
ReSharper has a whole set of nice keyboard shortcuts , which includes Ctrl + Shift + , for View Recent Edits .
This overwrites the Zoom Out half of the default Visual Studio zoom keyboard shortcuts (thanks Carlos Muñoz ):
Ctrl + Shift + . to zoom in and Ctrl + Shift + , to zoom out.
They don’t keep an alternative for Zoom Out, and unlike most tools I know that allow for zooming, there is no keyboard accessible menu entry for Zoom Out in Visual Studio .
So you have to use your mouse to go in the lower left of your editor window in order to Zoom Out (thanks ashteele for putting that in an SO question ):
Or you can reconfigure the old shortcut (thanks Aaron Ransley ):
through Tools -> Options -> Environment -> Keyboard and map “View.ZoomIn” and “View.ZoomOut“
–jeroen
Posted in .NET , Development , Software Development , Visual Studio 11 , Visual Studio 2010 , Visual Studio 2013 , Visual Studio 2014 , Visual Studio and tools | Leave a Comment »
Posted by jpluimers on 2015/07/28
Shelving work into a shelveset is easy in Visual Studio. Until Visual Studio 2010 it was easy to find the shelveset .
As of Visual Studio 2012 this is much more difficult . To get the shelveset back in Visual Studio 2012 and up:
Go to the “Team Explorer” pane
Click the “Home” icon
Choose “Pending Changes”
Click the topmost “Actions” item
In the pop-up menu, click “Find Shelvesets”
Type a search phrase
–jeroen
via: Can anybody find the TFS “Unshelve” option in Visual Studio 2012? – Stack Overflow .
Posted in .NET , Development , Software Development , Visual Studio 11 , Visual Studio 2010 , Visual Studio 2013 , Visual Studio 2014 , Visual Studio and tools | Leave a Comment »
Posted by jpluimers on 2015/05/12
Boy, Microsoft made it hard to find the location of xsd.exe !
It is actually located like here:
C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\xsd.exe
But that is nowhere on the default path, nor in the registry.
What happens during installation of Visual Studio and/or the Microsoft SDK, is that the vsvars32.bat xsd.exe) to the PATH.
So the trick is to find the youngest Visual Studio first, then run the according vsvars32.bat, and then xsd.exe is on the path.
Learn more about bidirectional Unicode characters
:: Dynamically finds the installed xsd.exe, then calls it with the passed parameters
:: test these environment variables that have 110 or 120 in them (future enhancements: support more Visual Studio versions):
:: Visual Studio .NET 2002: VS70COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio .NET\Common7\Tools\
:: Visual Studio .NET 2003: VS71COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Common7\Tools\
:: Visual Studio 2005: VS80COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\Tools\
:: Visual Studio 2008: VS90COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Tools\
:: Visual Studio 2010: VS100COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\
:: Visual Studio 2012: VS110COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\
:: Visual Studio 2013: VS120COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\
:: They contain `vsvars32.bat` which will update the `PATH` so it includes where `xsd.exe` resides
setlocal enabledelayedexpansion
:: delayed expansion allows for the exclamation marks
:: see http://ss64.com/nt/delayedexpansion.html
:: see http://stackoverflow.com/questions/22857407/windows-batch-how-to-assign-variable-with-dynamic-name
for %%v in (70 71 80 90 100 110 120 130) do if not [!VS%%vCOMNTOOLS!]==[] set VSCOMNTOOLS=!VS%%vCOMNTOOLS!
call :do call "!VSCOMNTOOLS!vsvars32.bat"
call :do where xsd.exe
xsd.exe %*
endlocal
goto :eof
:do
echo %*
%*
goto :eof
–jeroen
via:
Read the rest of this entry »
Posted in .NET , .NET 2.0 , .NET 3.0 , .NET 3.5 , .NET 4.0 , .NET 4.5 , C# , C# 2.0 , C# 3.0 , C# 4.0 , C# 5.0 , C# 6 (Roslyn) , Development , Software Development , Visual Studio 11 , Visual Studio 2010 , Visual Studio 2013 , Visual Studio 2014 , Visual Studio and tools , XML/XSD , XSD | 1 Comment »
Posted by jpluimers on 2015/05/05
I wrote about the xsd.exe tool before to generate XSD from XML:
But it is much more than that, as it is a great way of generating .NET (not only C# and VB.NET code) from XSD files:
Long ago, xsd.exe used to come as part of Visual Studio , but now it is installed with the various Microsoft Windows SDK versions (of which some are downloadable ) which makes it harder to locate on your system.
The really bad thing is that Visual Studio cannot find XSD.exe as part of your project Build Events , as the PATH has not been set up correctly.
Starting xsd.exe from a Visual Studio Build Events
In my hunt for the xsd.exe location, I started with a small batch file to find the xsd.exe locations from the registry:
Read the rest of this entry »
Posted in .NET , Continuous Integration , Development , msbuild , Software Development , Visual Studio 2003 , Visual Studio 2005 , Visual Studio 2008 , Visual Studio 2010 , Visual Studio 2013 , Visual Studio 2014 , Visual Studio and tools , XML/XSD , XSD | 3 Comments »
Posted by jpluimers on 2015/04/30
Often I want to execute a TF.exe from the console, but don’t have the Visual Studio environment variables setup. Most of the times I want to run TF.exe from the most current Visual Studio installation, hence this TF.bat file figures out the location of it, then runs with the parameters passed to TF.bat: Read the rest of this entry »
Posted in .NET , Development , Software Development , Visual Studio 11 , Visual Studio 2005 , Visual Studio 2008 , Visual Studio 2010 , Visual Studio 2013 , Visual Studio 2014 , Visual Studio and tools | 1 Comment »
Posted by jpluimers on 2015/04/02
I’m going to experiment with this. Most likely the quality of the code samples will be the biggest factor in like/dislike result.
Visual Studio – Google+ .
–jeroen
Posted in .NET , .NET 3.0 , .NET 3.5 , .NET 4.0 , .NET 4.5 , C# , C# 3.0 , C# 4.0 , C# 5.0 , C# 6 (Roslyn) , Development , Software Development , Visual Studio 2010 , Visual Studio 2013 , Visual Studio 2014 , Visual Studio and tools | 1 Comment »
The Wiert Corner - irregular stream of stuff 