<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>msbuildshellex Work Item Rss Feed</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/List.aspx</link><description>msbuildshellex Work Item Rss Description</description><item><title>Created Issue: Got a strange message upon clicking any context menu item (e.g. "Build") [14170]</title><link>http://msbuildshellex.codeplex.com/WorkItem/View.aspx?WorkItemId=14170</link><description>The message is&amp;#58; &amp;#34;This file does not have a program associated with it for performing this action. Create an association in the Set Associations control panel.&amp;#34;&lt;br /&gt;&lt;br /&gt;Then nothing seems to happen.&lt;br /&gt;&lt;br /&gt;OS &amp;#61; Windows Vista&lt;br /&gt;</description><author>immitev</author><pubDate>Wed, 16 Sep 2009 09:07:47 GMT</pubDate><guid isPermaLink="false">Created Issue: Got a strange message upon clicking any context menu item (e.g. "Build") [14170] 20090916090747A</guid></item><item><title>Created Issue: Bug - Exception when adding new configuration</title><link>http://msbuildshellex.codeplex.com/WorkItem/View.aspx?WorkItemId=12751</link><description>- Open the Configuration dialog, New &amp;#34;Build x64&amp;#34;, Define the new &amp;#34;Build64&amp;#34;, configuration &amp;#34;Release X64&amp;#34;  - Click on &amp;#34;Add&amp;#34; button. Get Exception&lt;br /&gt;&lt;br /&gt;See the end of this message for details on invoking &lt;br /&gt;just-in-time &amp;#40;JIT&amp;#41; debugging instead of this dialog box.&lt;br /&gt;&lt;br /&gt;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42; Exception Text &amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&lt;br /&gt;System.NullReferenceException&amp;#58; Object reference not set to an instance of an object.&lt;br /&gt;   at Ardal.MSBuildShellExtension.Configurator.TargetControl.addButton_Click&amp;#40;Object sender, EventArgs e&amp;#41;&lt;br /&gt;   at System.Windows.Forms.Control.OnClick&amp;#40;EventArgs e&amp;#41;&lt;br /&gt;   at System.Windows.Forms.Button.OnClick&amp;#40;EventArgs e&amp;#41;&lt;br /&gt;   at System.Windows.Forms.Button.OnMouseUp&amp;#40;MouseEventArgs mevent&amp;#41;&lt;br /&gt;   at System.Windows.Forms.Control.WmMouseUp&amp;#40;Message&amp;#38; m, MouseButtons button, Int32 clicks&amp;#41;&lt;br /&gt;   at System.Windows.Forms.Control.WndProc&amp;#40;Message&amp;#38; m&amp;#41;&lt;br /&gt;   at System.Windows.Forms.ButtonBase.WndProc&amp;#40;Message&amp;#38; m&amp;#41;&lt;br /&gt;   at System.Windows.Forms.Button.WndProc&amp;#40;Message&amp;#38; m&amp;#41;&lt;br /&gt;   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage&amp;#40;Message&amp;#38; m&amp;#41;&lt;br /&gt;   at System.Windows.Forms.Control.ControlNativeWindow.WndProc&amp;#40;Message&amp;#38; m&amp;#41;&lt;br /&gt;   at System.Windows.Forms.NativeWindow.Callback&amp;#40;IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam&amp;#41;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42; Loaded Assemblies &amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&lt;br /&gt;mscorlib&lt;br /&gt;    Assembly Version&amp;#58; 2.0.0.0&lt;br /&gt;    Win32 Version&amp;#58; 2.0.50727.3053 &amp;#40;netfxsp.050727-3000&amp;#41;&lt;br /&gt;    CodeBase&amp;#58; file&amp;#58;&amp;#47;&amp;#47;&amp;#47;C&amp;#58;&amp;#47;Windows&amp;#47;Microsoft.NET&amp;#47;Framework&amp;#47;v2.0.50727&amp;#47;mscorlib.dll&lt;br /&gt;----------------------------------------&lt;br /&gt;MSBuildShellExtensionConfigurator&lt;br /&gt;    Assembly Version&amp;#58; 1.1.2.0&lt;br /&gt;    Win32 Version&amp;#58; 1.1.2.0&lt;br /&gt;    CodeBase&amp;#58; file&amp;#58;&amp;#47;&amp;#47;&amp;#47;C&amp;#58;&amp;#47;Program&amp;#37;20Files&amp;#47;MSBuildShellExtension&amp;#47;MSBuildShellExtensionConfigurator.exe&lt;br /&gt;----------------------------------------&lt;br /&gt;System.Windows.Forms&lt;br /&gt;    Assembly Version&amp;#58; 2.0.0.0&lt;br /&gt;    Win32 Version&amp;#58; 2.0.50727.3053 &amp;#40;netfxsp.050727-3000&amp;#41;&lt;br /&gt;    CodeBase&amp;#58; file&amp;#58;&amp;#47;&amp;#47;&amp;#47;C&amp;#58;&amp;#47;Windows&amp;#47;assembly&amp;#47;GAC_MSIL&amp;#47;System.Windows.Forms&amp;#47;2.0.0.0__b77a5c561934e089&amp;#47;System.Windows.Forms.dll&lt;br /&gt;----------------------------------------&lt;br /&gt;System&lt;br /&gt;    Assembly Version&amp;#58; 2.0.0.0&lt;br /&gt;    Win32 Version&amp;#58; 2.0.50727.3053 &amp;#40;netfxsp.050727-3000&amp;#41;&lt;br /&gt;    CodeBase&amp;#58; file&amp;#58;&amp;#47;&amp;#47;&amp;#47;C&amp;#58;&amp;#47;Windows&amp;#47;assembly&amp;#47;GAC_MSIL&amp;#47;System&amp;#47;2.0.0.0__b77a5c561934e089&amp;#47;System.dll&lt;br /&gt;----------------------------------------&lt;br /&gt;System.Drawing&lt;br /&gt;    Assembly Version&amp;#58; 2.0.0.0&lt;br /&gt;    Win32 Version&amp;#58; 2.0.50727.3053 &amp;#40;netfxsp.050727-3000&amp;#41;&lt;br /&gt;    CodeBase&amp;#58; file&amp;#58;&amp;#47;&amp;#47;&amp;#47;C&amp;#58;&amp;#47;Windows&amp;#47;assembly&amp;#47;GAC_MSIL&amp;#47;System.Drawing&amp;#47;2.0.0.0__b03f5f7f11d50a3a&amp;#47;System.Drawing.dll&lt;br /&gt;----------------------------------------&lt;br /&gt;DomainModel&lt;br /&gt;    Assembly Version&amp;#58; 1.1.2.0&lt;br /&gt;    Win32 Version&amp;#58; 1.1.2.0&lt;br /&gt;    CodeBase&amp;#58; file&amp;#58;&amp;#47;&amp;#47;&amp;#47;C&amp;#58;&amp;#47;Program&amp;#37;20Files&amp;#47;MSBuildShellExtension&amp;#47;DomainModel.DLL&lt;br /&gt;----------------------------------------&lt;br /&gt;&lt;br /&gt;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42; JIT Debugging &amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&amp;#42;&lt;br /&gt;To enable just-in-time &amp;#40;JIT&amp;#41; debugging, the .config file for this&lt;br /&gt;application or computer &amp;#40;machine.config&amp;#41; must have the&lt;br /&gt;jitDebugging value set in the system.windows.forms section.&lt;br /&gt;The application must also be compiled with debugging&lt;br /&gt;enabled.&lt;br /&gt;&lt;br /&gt;For example&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#60;configuration&amp;#62;&lt;br /&gt;    &amp;#60;system.windows.forms jitDebugging&amp;#61;&amp;#34;true&amp;#34; &amp;#47;&amp;#62;&lt;br /&gt;&amp;#60;&amp;#47;configuration&amp;#62;&lt;br /&gt;&lt;br /&gt;When JIT debugging is enabled, any unhandled exception&lt;br /&gt;will be sent to the JIT debugger registered on the computer&lt;br /&gt;rather than be handled by this dialog box.&lt;br /&gt;</description><author>codemaniac</author><pubDate>Thu, 05 Mar 2009 00:21:22 GMT</pubDate><guid isPermaLink="false">Created Issue: Bug - Exception when adding new configuration 20090305122122A</guid></item><item><title>Created Issue: Runtime error when editor not found</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=11477</link><description>When specifying an editor exe file through the Configurator, the double click action in the error list fails, if the specified editor does not exist.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Thu, 16 Oct 2008 06:00:34 GMT</pubDate><guid isPermaLink="false">Created Issue: Runtime error when editor not found 20081016060034A</guid></item><item><title>Commented Feature: vdproj should be supported by using devenv</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=4827</link><description>vdproj projects are not supported by msbuild. MSBuildShellExtension could support this filetype by executing devenv.exe rather than msbuild.exe.&lt;br /&gt;&lt;br /&gt;If this should be supported, MSBuildShellExtension needs to parse the output from calling devenv, in order to show errors and warnings from the build.&lt;br /&gt;Comments: ** Comment from web user: lextm ** &lt;p&gt;MSBuildShellExtension should focus on MSBuild.exe, other than devenv.exe which only is installed with the paid Visual Studio users. Maybe someone can create a separate DevEnvShellExtension somewhere.&lt;/p&gt;</description><author>lextm</author><pubDate>Fri, 29 Aug 2008 12:58:26 GMT</pubDate><guid isPermaLink="false">Commented Feature: vdproj should be supported by using devenv 20080829125826P</guid></item><item><title>CLOSED ISSUE: Can't use MsBuildExtension for Vista Home Premium,  VS2008 Express  and .Net 3.5</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=9661</link><description>I get this comment&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#34;Build project could not be resolved. This error is caused by a poorly created API for MSBuild tools like MSBuildShellExtension. Sorry &amp;#58;&amp;#40;&amp;#34;&lt;br /&gt;&lt;br /&gt;When I click on this error in the Error List&amp;#58; &lt;br /&gt;&lt;br /&gt;Filformatets version kan ikke genkendes. MSBuild kan kun l&amp;#230;se l&amp;#248;sningsfiler mellem versionerne 7.0 og 9.0 begge inklusive.&lt;br /&gt;&lt;br /&gt;What is wrong&amp;#63;&lt;br /&gt;&lt;br /&gt;&amp;#47;JRO&lt;br /&gt;Comments: This where never an issue. You have to configure the tool to build with .NET 3.5 manually. I would like to be able to figure out which version of .NET to use automatically in a future version.</description><author>ThomasArdal</author><pubDate>Tue, 27 May 2008 06:58:03 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Can't use MsBuildExtension for Vista Home Premium,  VS2008 Express  and .Net 3.5 20080527065803A</guid></item><item><title>COMMENTED ISSUE: Can't use MsBuildExtension for Vista Home Premium,  VS2008 Express  and .Net 3.5</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=9661</link><description>I get this comment&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#34;Build project could not be resolved. This error is caused by a poorly created API for MSBuild tools like MSBuildShellExtension. Sorry &amp;#58;&amp;#40;&amp;#34;&lt;br /&gt;&lt;br /&gt;When I click on this error in the Error List&amp;#58; &lt;br /&gt;&lt;br /&gt;Filformatets version kan ikke genkendes. MSBuild kan kun l&amp;#230;se l&amp;#248;sningsfiler mellem versionerne 7.0 og 9.0 begge inklusive.&lt;br /&gt;&lt;br /&gt;What is wrong&amp;#63;&lt;br /&gt;&lt;br /&gt;&amp;#47;JRO&lt;br /&gt;Comments: ** Comment from web user: pjerrotluna ** &lt;p&gt;This is fixed. &lt;br /&gt;I have to go in the configuration and for all extensions choose v3.5. Then every compiles for .Net 3.5 and Visual Studio 2008 C&amp;#35; Express.&lt;br /&gt;Please mark this issue fixed, Thomas Ardal.&lt;br /&gt;And thanks again for this amazing tool.&lt;/p&gt;</description><author>pjerrotluna</author><pubDate>Thu, 03 Apr 2008 20:34:22 GMT</pubDate><guid isPermaLink="false">COMMENTED ISSUE: Can't use MsBuildExtension for Vista Home Premium,  VS2008 Express  and .Net 3.5 20080403083422P</guid></item><item><title>CREATED ISSUE: Can't use MsBuildExtension for Vista Home Premium,  VS2008 Express  and .Net 3.5</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=9661</link><description>I get this comment&amp;#58;&lt;br /&gt;&lt;br /&gt;&amp;#34;Build project could not be resolved. This error is caused by a poorly created API for MSBuild tools like MSBuildShellExtension. Sorry &amp;#58;&amp;#40;&amp;#34;&lt;br /&gt;&lt;br /&gt;When I click on this error in the Error List&amp;#58; &lt;br /&gt;&lt;br /&gt;Filformatets version kan ikke genkendes. MSBuild kan kun l&amp;#230;se l&amp;#248;sningsfiler mellem versionerne 7.0 og 9.0 begge inklusive.&lt;br /&gt;&lt;br /&gt;What is wrong&amp;#63;&lt;br /&gt;&lt;br /&gt;&amp;#47;JRO&lt;br /&gt;</description><author>pjerrotluna</author><pubDate>Fri, 14 Mar 2008 16:50:49 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Can't use MsBuildExtension for Vista Home Premium,  VS2008 Express  and .Net 3.5 20080314045049P</guid></item><item><title>CREATED ISSUE: Column reorder should be supported</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=9481</link><description>The order should be saved as well.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Tue, 04 Mar 2008 14:14:25 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Column reorder should be supported 20080304021425P</guid></item><item><title>CREATED ISSUE: Column width in error list logger should be saved</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=9480</link><description>Same as window size.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Tue, 04 Mar 2008 14:13:34 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Column width in error list logger should be saved 20080304021334P</guid></item><item><title>CLOSED FEATURE: MSBuildShellExtension should support .NET 3.5</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8639</link><description>MSBuildShellExtension should support .NET 3.5&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Sat, 01 Mar 2008 08:56:07 GMT</pubDate><guid isPermaLink="false">CLOSED FEATURE: MSBuildShellExtension should support .NET 3.5 20080301085607A</guid></item><item><title>CLOSED FEATURE: Error list window should show number of errors and warnings in title</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8890</link><description>This way you can minimize the window and still track any errors and&amp;#47;or warnings while building and you doing something else.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Wed, 27 Feb 2008 19:15:45 GMT</pubDate><guid isPermaLink="false">CLOSED FEATURE: Error list window should show number of errors and warnings in title 20080227071545P</guid></item><item><title>CLOSED ISSUE: Error list should show before letting the build continue</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8879</link><description>The build starts before showing the error list window, which can cause some weird errors where warnings are displayed, even though the warnings button is disabled, the error list window do not show on small projects etc.&lt;br /&gt;&lt;br /&gt;Show window before letting build continue.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Wed, 27 Feb 2008 19:15:12 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Error list should show before letting the build continue 20080227071512P</guid></item><item><title>CLOSED ISSUE: Runtime error in configurator if extensions is selected before targets</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8814</link><description>If the user clicks the extensions icon before having selected the targets icon, the configurator crashes.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Wed, 27 Feb 2008 19:14:10 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Runtime error in configurator if extensions is selected before targets 20080227071410P</guid></item><item><title>CREATED FEATURE: Import/Export settings to/from Configurator</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=9014</link><description>It would be cool to be able to export settings from the configurator and import the export file in a configurator on another machine.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Thu, 06 Dec 2007 12:20:29 GMT</pubDate><guid isPermaLink="false">CREATED FEATURE: Import/Export settings to/from Configurator 20071206122029P</guid></item><item><title>CREATED ISSUE: Double click on item in error list should show the file in the choosen editor even though the build file is not known</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8917</link><description>When double clicking a file in the error list window, an error dialog is shown if MSBuildShellExtension cannot find the buildfile containing the failing file. If the buildfile cannot be found, the choosen tool should open with the file instead.&lt;br /&gt;&lt;br /&gt;Example&amp;#58; If choosen Notepad as default editor, and build file cannot be found, an error dialog is shown. In this case, the tool could open the failing file in Notepad directly.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Thu, 29 Nov 2007 14:25:47 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Double click on item in error list should show the file in the choosen editor even though the build file is not known 20071129022547P</guid></item><item><title>CREATED ISSUE: Error list window should show number of errors and warnings in title</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8890</link><description>This way you can minimize the window and still track any errors and&amp;#47;or warnings while building and you doing something else.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Wed, 28 Nov 2007 14:04:52 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Error list window should show number of errors and warnings in title 20071128020452P</guid></item><item><title>CREATED ISSUE: Error list should show before letting the build continue</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8879</link><description>The build starts before showing the error list window, which can cause some weird errors where warnings are displayed, even though the warnings button is disabled, the error list window do not show on small projects etc.&lt;br /&gt;&lt;br /&gt;Show window before letting build continue.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Mon, 26 Nov 2007 17:28:34 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Error list should show before letting the build continue 20071126052834P</guid></item><item><title>CREATED ISSUE: Runtime error in configurator if extensions is selected before targets</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8814</link><description>If the user clicks the extensions icon before having selected the targets icon, the configurator crashes.&lt;br /&gt;</description><author>ThomasArdal</author><pubDate>Sun, 25 Nov 2007 15:41:55 GMT</pubDate><guid isPermaLink="false">CREATED ISSUE: Runtime error in configurator if extensions is selected before targets 20071125034155P</guid></item><item><title>CLOSED ISSUE: Verbosity on targets is not saved</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8612</link><description>If another verbosity is choosen on a target, the new verbosity is never saved.&lt;br /&gt;Comments: Fixed in 1.1.1.</description><author>ThomasArdal</author><pubDate>Sun, 25 Nov 2007 14:57:20 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Verbosity on targets is not saved 20071125025720P</guid></item><item><title>CLOSED ISSUE: Removed editors are not deleted from registry</title><link>http://www.codeplex.com/msbuildshellex/WorkItem/View.aspx?WorkItemId=8587</link><description>Removed editors are not deleted from registry.&lt;br /&gt;Comments: Fixed in 1.1.1.</description><author>ThomasArdal</author><pubDate>Sun, 25 Nov 2007 14:57:04 GMT</pubDate><guid isPermaLink="false">CLOSED ISSUE: Removed editors are not deleted from registry 20071125025704P</guid></item></channel></rss>