Hello Andreas Ljungström (aljungstroem),

After taking a look at the support tickets (to check what so far had been suggested) I have done a little research on this issue and it appears that the BAML/XAML files are connected with the .net framework version which requires the (missing) dependency file and which would throw the error....

'The invocation of the constructor on type 'XXXXXXXXXXXXX' that matches the specified binding constraints threw an exception.

If you are maybe running an older Windows version (XP/Vista for instance), then the problem could be that the older OS versions are unable to support the new dependencies in .net.

As you have already stated- you can run Studio without issues on other machines- my suggestion would be to ensure you are running at least Windows 7 (we cannot support anything older) with all updates installed and applied and to ensure that you have at least .NET framework 4.5.2 installed.

Please let me know if any of this helped.

Hello Andreas Ljungström 

Thanks for getting back to me.

As this issue only happens on your machine (other colleagues share the same set up) and you appear to be up to date on the .net framework and are running a supported OS, then we can only surmise its a local issue- a small piece of program maybe that has not been installed properly or a conflict with a different program (maybe you are running something that your colleagues are not (or vice versa). There are just so many variables and possibilities and it appears to be something i believe no one else has experienced.

I know this can be a real pain when you are restricted to a Corp group policy and do not have admin rights, but unless someone else has a suggestion, I think the only real option(s) would be what has been suggested above.

Unknown said:

One of our supporters suggested a complete SDL suite removal (I run 2015 as well) and then a Registry cleanup, followed by a clean install.
Another supporter suggested a complete reinstallation of Windows and all applications, including an upgrade to Win10.

Maybe try solution 1 first (least time costly) before having to go all out on suggestion 2.

Hello Andreas Ljungström 

Thanks for getting back to me.

As this issue only happens on your machine (other colleagues share the same set up) and you appear to be up to date on the .net framework and are running a supported OS, then we can only surmise its a local issue- a small piece of program maybe that has not been installed properly or a conflict with a different program (maybe you are running something that your colleagues are not (or vice versa). There are just so many variables and possibilities and it appears to be something i believe no one else has experienced.

I know this can be a real pain when you are restricted to a Corp group policy and do not have admin rights, but unless someone else has a suggestion, I think the only real option(s) would be what has been suggested above.

Unknown said:

One of our supporters suggested a complete SDL suite removal (I run 2015 as well) and then a Registry cleanup, followed by a clean install.
Another supporter suggested a complete reinstallation of Windows and all applications, including an upgrade to Win10.

Maybe try solution 1 first (least time costly) before having to go all out on suggestion 2.