<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Visual Studio on ZeroSharp</title><link>https://www.zerosharp.com/blog/categories/visual-studio/</link><description>Recent content in Visual Studio on ZeroSharp</description><generator>Hugo</generator><language>en-gb</language><copyright>Copyright © 2012–{year} Robert Anderson</copyright><lastBuildDate>Mon, 03 Aug 2015 15:35:00 +0100</lastBuildDate><atom:link href="https://www.zerosharp.com/blog/categories/visual-studio/index.xml" rel="self" type="application/rss+xml"/><item><title>A strange error message from Visual Studio 2015</title><link>https://www.zerosharp.com/a-strange-error-message-from-visual-studio-2015/</link><pubDate>Mon, 03 Aug 2015 15:35:00 +0100</pubDate><guid>https://www.zerosharp.com/a-strange-error-message-from-visual-studio-2015/</guid><description>&lt;p&gt;When I recently upgraded to Visual Studio 2015, everything seemed to go very smoothly except that whenever I debugged my main application I got a dialog window with the following strange error:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;The procedure entry point could not be located in the dynamic link library C:\...\bin\Debug\netutils.dll.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;After pressing &lt;code&gt;OK&lt;/code&gt; everything seemed to work as normal.&lt;/p&gt;
&lt;p&gt;After a considerable number of dead ends, I finally worked out that changing the name of the &lt;em&gt;NetUtils.dll&lt;/em&gt; assembly fixes the problem. It seems that Visual Studio 2015 gets confused with a Windows system assembly with the same name. I don&amp;rsquo;t know why it was never a problem with Visual Studio 2013, but I renamed the assembly and now everything is working fine.&lt;/p&gt;</description></item><item><title>Fixing slow debugging of ASP.NET applications</title><link>https://www.zerosharp.com/fixing-slow-debugging-of-asp-dot-net-applications/</link><pubDate>Wed, 03 Jun 2015 21:31:00 +0100</pubDate><guid>https://www.zerosharp.com/fixing-slow-debugging-of-asp-dot-net-applications/</guid><description>&lt;p&gt;For a while I&amp;rsquo;ve noticed an annoying slowness when debugging ASP.NET applications from Visual Studio. Just after every page load it takes about a second before the buttons become clickable. I noticed mostly when debugging XAF applications, perhaps because the pages are quite complex.&lt;/p&gt;
&lt;p&gt;Turns out the culprit is something called &lt;a href="http://www.asp.net/visual-studio/overview/2013/using-browser-link"&gt;Browser Link&lt;/a&gt; which was introduced in Visual Studio 2013. It&amp;rsquo;s enabled by default.&lt;/p&gt;
&lt;p&gt;To turn it off you can turn it off from the menu:&lt;/p&gt;</description></item><item><title>Provisioning a new development machine with BoxStarter</title><link>https://www.zerosharp.com/provisioning-a-new-development-machine-with-boxstarter/</link><pubDate>Tue, 25 Feb 2014 15:29:00 +0100</pubDate><guid>https://www.zerosharp.com/provisioning-a-new-development-machine-with-boxstarter/</guid><description>&lt;p&gt;I&amp;rsquo;ve been playing around with &lt;a href="http://boxstarter.org/"&gt;Boxstarter&lt;/a&gt; to configure my entire development environment with hardly any user intervention.&lt;/p&gt;
&lt;img class="img-right" src="https://www.zerosharp.com/images/blog/boxstarter-001.png" alt="300"&gt;
&lt;p&gt;Here are the steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Install Windows 8.1 on a new machine.&lt;/li&gt;
&lt;li&gt;Login.&lt;/li&gt;
&lt;li&gt;Open a command prompt and enter the following.&lt;/li&gt;
&lt;/ol&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;START http://boxstarter.org/package/nr/url?http://bit.ly/1kapDXI
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;That&amp;rsquo;s it!&lt;/p&gt;
&lt;p&gt;Boxstarter will self-install via ClickOnce, asking for various confirmations and ultimately it will prompt you for your login password. (This gets saved and encrypted to allow for unattended reboots and re-logins during the installation). Then the real magic begins. Boxstarter downloads and installs all your tools and configures your environment, rebooting as necessary. An hour later your full development setup is installed, including Visual Studio 2013, any VS extensions, any other programs and tools, all the browsers you need, all critical Windows updates, etc. You just saved yourself a couple of days of work and a lot of hassle.&lt;/p&gt;</description></item></channel></rss>