Re: WPF broken after .NET update

2018-05-30 Thread Greg Keogh
>
> Server updates installed?
>

Nah, it's had the windows update icon in the tray for months.

If yes maybe uninstall .net and reinstall.
>

Yep, that fixed it, somehow!

I uninstalled 4.6.1. In VS2017 I created a setup project for my WPF
program, specifying a dependency upon 4.6.1. When I run the installer EXE
launcher (not the MSI) it detected the missing Framework and I said yes to
"download from the vendor's website". After that it all came good. So I was
rescued by an automated reinstall.

I guess the reinstall used a different 4.6.1 installer?! In the morning I
used the "4.6.1 offline installer", which seemed correct. Uh, who knows?

*Greg K*


Re: WPF broken after .NET update

2018-05-30 Thread Tom Rutter
Server updates installed?
If yes maybe uninstall .net and reinstall.

On Wed, 30 May 2018 at 16:27, Greg Keogh  wrote:

> Folks, I just installed .NET Framework 4.6.1 redistributable on our
> development Win2008R2 server and rebooted. Now every WPF program crashes
> very early in startup here:
>
> Exception Info: System.InvalidOperationException
>at MS.Internal.NativeWPFDLLLoader.LoadCommonDLLsAndDwrite()
>
> It doesn't matter what runtime version the program targets, or how vanilla
> simple it is. Every WPF program dies. Web searches produce nothing useful
> to far, so I'm wondering if anyone has seen this before.
>
> *Greg K*
>


WPF broken after .NET update

2018-05-30 Thread Greg Keogh
Folks, I just installed .NET Framework 4.6.1 redistributable on our
development Win2008R2 server and rebooted. Now every WPF program crashes
very early in startup here:

Exception Info: System.InvalidOperationException
   at MS.Internal.NativeWPFDLLLoader.LoadCommonDLLsAndDwrite()

It doesn't matter what runtime version the program targets, or how vanilla
simple it is. Every WPF program dies. Web searches produce nothing useful
to far, so I'm wondering if anyone has seen this before.

*Greg K*