Jump to content
Gerard Murphy

Exception thrown when Semantic Merge is invoked via Visual Studio TFS integration.

Recommended Posts

Hi,

 

I'm using Visual Studio 2010 on a PC running Windows XP Professional 2002, Service Pack 3.

 

TFS is used as the version control package (not my choice, I hasten to add - this is at a client site).

 

I've downloaded a trial version of Semantic Merge 1.0.54.0 and installed it without any problems in my user folder, as recommended.

 

I have followed the instructions for configuring TFS to use it for both comparison and merging - this was quite straightforward.

 

However, on attempting to carry out a diff or merge, I see a dialog caused by the following exception:-

 

System.Windows.Baml2006.TypeConverterMarkupExtension. Nothing else happens after that, although Visual Studio is still running.

 

If I run Semantic Merge explicitly via the Start Menu, it successfully launches the initial splash screen and landing screen; this time, if I try to run it on a specific folder (such as the example shipped with it), I see the same exception - but it does proceed to the actual diff or merging step as soon as I dismiss the exception dialog.

 

So to summarise, Semantic Merge in standalone mode works despite the exception being thrown, but the Visual Studio / TFS integration is broken by the same exception.

 

I'd like to try Semantic Merge and see if I can get some buy-in at the client site, but as it stands, this is a showstopper for me.

Share this post


Link to post
Share on other sites

Hi,

 

I´ve just performed a test on my Windows 7 virtual machine without issues. Do you have .net 4 installed on your Win XP ?  

 

Regards,

Carlos

Share this post


Link to post
Share on other sites

Hi Carlos,

 

Thanks for getting back to me.

 

I have .NET 4 Client Profile, .Net 4 Extended and .NET 4 Multi-Targeting Pack all installed, as well as .Net 3.0 SP 2, 3.5 SP2, .2.0 SP 2 and 1.1.

 

Trawling around Stack Overflow suggests that even with .NET 4 installed, there are still subtle differences in behaviour with WPF support on XP that can cause this problem - a common culprit being .PNG versus .JPG file support, although this is all rampant speculation on my part.:-)

 

Regards,

 

Gerard

Share this post


Link to post
Share on other sites

Hi Gerard,

 

We have reproduced the issue using Windows XP + Semantic Merge. I´ve created a task to fix the compatibility as soon as possible. Sorry for the inconvenience.

 

Regards,

Carlos

Share this post


Link to post
Share on other sites

Yes, it seems the issue is only being reproduced on old OSs. Probably some small thing about the visual style.

 

We started a new SPRINT today and we add this to the list. Hopefully we'll have it ready this week.

Share this post


Link to post
Share on other sites

Hi!

 

it's almost ready, the bugfix is done but we need to validate it and release it.

 

At the end of the day it was a problem with the app icon!! The icon image is embedded so I'm afraid there's no workaround.

Share this post


Link to post
Share on other sites

Hi Gerard,

 

We are releasing today a new Semantic Merge version with some fixes to run on Win XP and Win Server 2008  operating systems. The thing is that we have upgraded the required .net framework to .net 4.5

.

From our release notes:

 

--------------------

Bug fixed: SemanticMerge did not start properly in Windows XP or Windows 2008 server. An "Image format is unrecognized" was thrown.

--------

New: the new Roslyn libraries are now used on Windows and Mac (Linux will join soon).
New: C# 5 support on Windows and Mac! The upgrade to the new Roslyn libraries includes support for the newer C# version. This closes one of the top UserVoice requests: http://plasticscm.uservoice.com/forums/196398-mergebegins/suggestions/4318628-c-5-support. It requires .Net 4.5 framework.
-----------
 
The .net 4.5 upgrade is mainly to support C# 5 using the new Roslyng libraries.
 
But I´m not sure if it´s possible to install .net 4.5 on Windows XP.  Do you have this information?
 
In case you can´t install .net 4.5 version, we will generate an independent release for you including the Win XP fix but not the .net 4.5 related changes (.net 4 would be needed)
 
Best regards,
Carlos 

Share this post


Link to post
Share on other sites

Hi Carlos - I think you are correct, we won't be able to to this on the client's XP boxes, .NET 4 is as high as we can go on XP.

 

Could you produce a version targeting .NET 4 with the image format fix? We can get by without the full C# 5 support at the client site.

 

 

Regards,

 

Gerard

Share this post


Link to post
Share on other sites

Hi,

 

Sorry for the delay, we are going to generate to release for .net 4. Hopefully it will be ready on Friday. I will contact with you as soon it´s released.

 

Best regards,

Carlos

Share this post


Link to post
Share on other sites

Excellent, many thanks to the team at Plastic for this - your support is appreciated.

 

I'm away from the client site this week, but I'll give this a try next week and let you know how it goes.

 

Cheers,

 

Gerard

Share this post


Link to post
Share on other sites

Just to close off this thread, I can confirm that the .NET 4 version works just fine under Windows XP - you just made another license sale. :-)

 

Thanks again for sorting this out.

 

Kind Regards,

 

Gerard

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×