Hi,
Our app is writen in .NET 3.5 and for some clients or with some our modules
we require the app to run in .NET 4.0 runtime (in app.config by:
*supportedRuntime version=v4.0 sku=.NETFramework,Version=v4.0/*).
The problem is only with 4.0 runtime. When we not force the app to run in
4.0
In fact Milan,
but if I use LINQPad to test the WCF script it works, but the line you
reported is present in the LINQPad configuration file and also in our
application.
In LINQPad it works, in out application doesn't.
Our application is written using .NET 4.0.
Any idea?
Thank you.
On
Thanks for the insight Hammett, wasn't aware the other teams weren't under
the same umbrella as the fx team.
On Tue, May 5, 2015 at 6:55 PM, hammett hamm...@gmail.com wrote:
Different layers of the framework receive different levels of scrutiny
towards backward compatibility. The core fx, that
I just created an issue for this problem:
http://github.com/castleproject/Windsor/issues/84
On Monday, March 30, 2015 at 5:01:23 PM UTC+2, Filip Kinsky wrote:
The same error ocurs after recent Windows 10 Windows Update when ASP.NET
4.6 runtime upgrade was delivered btw.
On Mon, Mar 30,
I'm running into exactly the same issue. Would really appreciate a
workaround.
Thanks!
On Monday, March 23, 2015 at 2:23:46 PM UTC, Filip Kinsky wrote:
Hello,
I was trying Visual Studio 2015 CTP and got ASP.NET 4.6 upgrade during
the VS installation. I use Windsor WCF integration, which
