As far as I can make out, in WIF 1.0, Windows Identity directly derives from IIdentity. In WIF 4.5, Windows Identity derives from ClaimsIdentity which implements IIdentity.
How does this affect migrating my WIF 1.0 applications?
Is everything backward compatible or are there any gotchas?
Can I have both libraries on my development machine?
There are breaking changes, see the Guidelines for Migrating an Application Built Using WIF 3.5 to WIF 4.5 for details.
Related
I tried very hard to find and could not.
I need OAuth 1.0 since I need to use intuit QB which not support oauth 2.0 yet.
thanks!
I had the same struggle the past few days in finding an implementation for .NET Core that supports OAuth 1.0. The library from Chilkat may be the only one out there. Not sure if the OAuth API inside the library requires the commercial license or not.
https://www.chilkatsoft.com/refdoc/csOAuth1Ref.html
https://www.chilkatsoft.com/dotnet-core.asp
Another solid option is to use the portable version RestSharp which has a built-in OAuth1Authenticator: https://www.myget.org/feed/restsharp-portable/package/nuget/FubarCoder.RestSharp.Portable.OAuth1
I used OAuth.DotNetCore for OAuth 1.0 with .Net Core 2.1, it worked fine.
https://www.nuget.org/packages/OAuth.DotNetCore/
I am using ASP Identity 2.2.x (2.x) targeting .NET 4.6/system.web.mvc 5.2.3 which in reality seems like its MVC 5 (another confusing ball game for me).
Now that I saw ASP Identity 3.0 released here and here, I was looking to upgrade, but don't know if its simple replace or more complicated -
Can I upgrade to 3.0 inside the current 4.6 target run time, or do I need DNX?
Is 4.6 considered ASP MVC 5 (yes, I am using System.Web.Mvc 5.2.3), so this should be compatible based on the the two links above, right?
What does Identity 3.x buy me thats not in 2.x
What does it involve, has anyone cared to venture :)
I like the HttpClient in ASP.NET Web API. Can I use it in 3.5 or 2.0. I mean in any .NET Framework application versions before 4.0. Actually, I have a ASP.NET Web API app in ASP.NET 4.0. I need to consume this app from a device built in 3.5 framework. I know I can use WebClient/WebRequest, But It will be great If I can use HttpClient stuffs.
According to this,
WebAPI requires .net 4. You can't use it on .net 3.5 (sp1 or not).
You also can't use the preview releases for production code as you
don't have a "go-live" license, so even if you could get it to work,
it wouldn't be legal. You need to use at least the ASP.NET WebAPI Beta
to get a go-live license.
And according to this,
The HttpClient library was initially introduced in the "WCF REST
Starter Kit" project, so you can download it from there. This project
isn't supported anymore (most of its functionality has either made it
into the framework or is now part of the Web API project), but the
HttpClient from there works quite well.
Ideally your HttpClient project should be completely separate from your service project. I would keep the service(s) project as it is in 2.0 or 3.5 and create a 4.0 project with HttpClient and make HTTP calls.
The only minor issue here is implicit model binding. Here you can use a Model dll or consume the 3.5 model classes in the 4.0 client project. But the JsonObject binding should also work seamlessly for json resonses.
My host supports
ASP
ASP.NET v1.0/2.0
ASP.NET Ajax
Access Database Support
MS Server Database Support (SQL Server)
I know by copying some of the files it's possible to run a .NET 3.5 Windows Forms application without .NET 3.5 installed on the client. Does the same hold for ASP.NET 3.5 MVC 1.0? Does MVC 1.0 support .NET 2.0?
My host is Go Daddy in case it helps or matters.
Mostly. Scott Hanselman has an article describing exactly how to do this. He notes:
This workaround is offered with exactly zero warranty or support. It's as-is, just an FYI on the blog. If this hack deletes files or kills your cat, you have been warned. No whining.
In practice, no one really knows what might break. Microsoft didn't test this.
This just flat might not work for you. Sorry.
The trick:
You can copy System.Core from your .NET 3.5 development machine (this is the machine running VS2008 that you're developing on) to the /bin folder on your .NET 2.0 SP1 machine. It's gotta be running .NET Framework 2.0 SP1 or this won't work. System.Core is probably somewhere around "C:\windows\assembly\GAC_MSIL\System.Core\3.5.0.0__b77a5c561934e089" on your machine, but you're a bad person for even asking.
I have searched various online resources and found conflicting information about the possibility of ASP.NET MVC 1.0 web apps running against the latest build of Mono (2.4.x). According to the Mono site, ASP.NET 2.0 is supported. According to Microsoft, ASP.NET MVC 1.0 requires the 3.5 version of the framework. From what I've read, ASP.NET 3.5 makes use of the 2.0 framework under the hood.
Has anyone got an ASP.NET MVC 1.0 web app running on Linux with Apache using mod_mono ?
Thanks
Yes, though you'll want to update the latest bugfix release for best compatibility. Note that Mono 2.4.2.3 actually includes the real ASP.NET MVC library, which was open-sourced by Microsoft under the MS-PL license.
The relationship between .NET and Mono version numbers is very complicated, as there is no direct mapping between .NET versions and features that Mono has implemented. .NET versions aren't exactly straightforward either, as 3.0 was simply additional assemblies added to the 2.0 framework, and similarly, 3.5 is additions to the 2.0SP1 framework - and the 3.5 assemblies do not depend on the 3.0 ones.
Mono features are driven by demand, using data collected using the Mono Migration Analyser.
For example, Mono has supported core .NET 2.0 features like generics since 2005 or so, but only with Mono 2.0 were the Windows Forms 2.0 and ASP.NET 2.0 components considered feature-complete - except for Web Parts, which will likely never be implemented due to low demand. And there are a couple of very Windows-specific features, like System.Management, which will also likely never be implemented as they simply cannot be mapped to non-Windows systems. Apart from such caveats, 2.0 support is now very complete.
Mono 2.0 also included full C# 3, LINQ-to-objects and LINQ-to-XML support, which are features from the .NET 3.5 framework. With Mono 2.4, the ASP.NET 3.5 features are essentially feature complete, and the only major missing 3.5 feature is LINQ-to-SQL, which should be in Mono 2.6. However, there's still no support for the .NET 3.0 assemblies - WCF, WPF, WF. WCF is being worked on but there are no plans for WPF at this time - some degree of WPF compatibility is provided via Moonlight, the Silverlight implementation.