Posted tagged ‘WPF’

WPF Application Issue Upgrading 2008 to 2010.

July 30, 2010

Just ran into another upgrade issue moving to Visual Studio 2010.  This time it was with a WPF Application.  When I went to open the properties window for the application in Visual Studio 2010 it gave me the error:

“An error occurred trying to load the project properties window.  Close the window and try again.  Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))”

Ugh.

I did a bit of searching to find the answer but then remembered that I had a some luck the other day in a similar situation with Windows Azure that I was able to resolve by comparing a new project file with the one I had.  What I found was that the configuration property groups were missing.

Solution

Copy the configuration property groups from the new project file to the one that does not work.  You will need to update the configuration setting if you have changed them from the defaults.  If you did take a backup that would be the best place to get your setting values from, however, consider that these groups may have gone missing in the first place due to some invalid setting value.

Here is an example of the standard configuration property groups for both Debug and Release on x86.

<PropertyGroup Condition=” ‘$(Configuration)|$(Platform)’ == ‘Debug|x86’ “>
<PlatformTarget>x86</PlatformTarget>
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<Optimize>false</Optimize>
<OutputPath>bin\Debug\</OutputPath>
<DefineConstants>DEBUG;TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
</PropertyGroup>
<PropertyGroup Condition=” ‘$(Configuration)|$(Platform)’ == ‘Release|x86’ “>
<PlatformTarget>x86</PlatformTarget>
<DebugType>pdbonly</DebugType>
<Optimize>true</Optimize>
<OutputPath>bin\Release\</OutputPath>
<DefineConstants>TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
</PropertyGroup>

Hope this will save you some hair!

Advertisements

Props to Karl Shifflett

June 14, 2009

I just attended the WPF – Line of Business conference in Chicago where Karl Shifflett was presenting.  The conference was incredible, probably the best I have attended and I hope to post on that later (but no promises).  Right now, I felt compelled to give props to Karl.  This guy is so enthusiastic about WPF he not only gets you more excited about this awesome product, he inspires you.  Oh yeah, he is very knowlegable, but there are lots of knowlegable people.  Karl takes it above and beyond,  by sharing his knowledge with you as if you were his best friend.  This guy takes your problem and turns it around for you as sample during the conference and even late into the night after you have gone as he did here for another attendee: http://karlshifflett.wordpress.com/2009/06/13/wpf-float-buttons-over-web-browser-control/.

Karl, you are the bomb!

What’s This? No Intellisense for WPF’s Xaml View.

March 18, 2008

I swear that the Xaml view had intellisense at one point. What is going on? Well apparently there is a problem where the intellisense stops working after installing an SDK or MSDN. In my case I believe this occurred after installing the .NET 2.0 Framework SDK. Great news though, there is a fix thanks to Brett Kilty of Microsoft.

To fix this you need to set the Default string value to the path of your TextMgrP.dll for the key “HKEY_CLASSES_ROOT\CLSID\{73B7DC00-F498-4ABD-AB79-D07AFD52F395}\InProcServer32”.

Here are the steps I executed to fix this:
1) Opened regedit
2) Searched for ‘{73B7DC00-F498-4ABD-AB79-D07AFD52F395}’
3) Expanded the key and clicked InProcServer32
4) The Default string was empty so I set it to ‘C:\Program Files\Common Files\Microsoft Shared\MSEnv\TextMgrP.dll’
5) Restarted Visual Studio
6) Smiled

btw – I’m running Visual Studio Professional 2008.

Link to Brett’s Post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2840817&SiteID=1

It’s Official: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2892404&SiteID=1 

Thanks Brett!