My google-fu is failing me on this one.
As a possible solution to Unit Testing .NET 3.5 projects using MStest in VS2010 (but I've put this in a seperate question because it's kind of unrelated):
Is there any information available regarding if/when .NET 4.0 support will be added to Windows Azure?
Cheers!
Support for .Net 4.0 was released with the June 2010 Azure SDK. The current SDK can be found here.
The indirect answer to your question to be found here:
http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/450add2a-ea93-4d79-b171-44072fa3c8d4/
In short, .NET 4 support in Windows Azure has not been announced.
Update: The Azure team announces that .NET 4 will be supported within 90 days of the .NET 4 RTM release date which was April 10. 2010.
http://blogs.msdn.com/windowsazure/archive/2010/04/07/upcoming-support-in-windows-azure-for-net-framework-4.aspx
Related
I've a asp.net web application written in VB using Visual Studio 2013. Can I make it multiplatform using .net core? Should I get Visual Studio 2017 or can stay using 2013? thank you!
Right now ASP.NET Core not available for VB.NET.
Please see this forum:
At the present time there is no firm or set time for this feature.
It's planned and has been mentioned as being on the roadmap, but at
present it doesn't look like it can even be supported.
See readmap.
You can use C# or F#.
And you need VS 2017 (or VS Code) for .NET Core.
Is it possible to use VS 2015 Update3, but not recommended, because they changed json project to MSBuild.
UPDATE: With .NET Core 2 release, now it's possible to use VB.NET in .NET Core, but not yet in ASP.NET:
:
I'm about to install .net 4.5 on a windows 2008 server with .net 2.0 and .net 4.0 already installed. I also have over 10 web forms applications running on iis. Microsoft said that the in-place installation of 4.5 over 4.0 is completely backwards compatible, but I still want to know if I should have any other concerns before I go ahead with the install. Is everything going to break? I'm so scared!
Be ready for the unexpected. You have several applications running in that server.
And see MSDN about that
.NET support dates are now linked to the support lifecycle of the parent product "As a Component, .NET takes the exact same Support Lifecycle as the parent product.":
http://blogs.technet.com/b/lifecycle/archive/2010/04/30/net-framework-3-5-sp1-and-later-now-supported-as-part-of-microsoft-windows.aspx
Based on the diagram on the following page I can see that .NET 3.5 is linked to Windows 7 and .NET 4.5 to Windows 8 http://msdn.microsoft.com/en-us/library/bb822049.aspx
However .NET 4.0 (based on the information at that link) isn't included on any client or server OS, so I'm confused as to what the end of support date is for it.
In my case, I've chosen to install .NET 4.0 onto a Windows 2008 server, but it didn't come preinstalled on that server, and can presumably run on Windows 2012, so I'm getting pretty lost as to what the official end of support date is for this.
Based on this page, not all versions have a parent product and .net 4.0 Extended support ends 12/01/2016.
Based on that page, Framework .Net 4.0 Extended support ends January 12, 2016.
.NET 4.5 is an in-place-upgrade and therefore replaces .NET 4.0. Consequently when I install .NET 4.5 with Visual Studio 2012 I can no longer develop applications for .NET 4.0.
As .NET 4.5 is not supported under Windows XP, how can I maintain my existing .NET 4.0 applications which still have to run under Windows XP after I installed Visual Studio 2012?
Until now I could always devlop .NET applications for every version, even .NET 1.1, as long as VS2003 was installed. I don't have a problem with Microsoft not supporting .NET 4.5 on XP, I think it's allright to cut off old stuff.
But as we have still customers using Windows XP, we need to be able to create .NET 4.0 programs at the same time as .NET 4.5.
EDIT:
I just had my first incompatibility issue: I installed VS 2012 on a Windows Server 2012. I created a project targeting .NET 4.0. In blend 4.0 I create a copy of a control template of a checkbox. The generated template contains references on colors which are available only under .NET 4.5. The solution cannot be compiled any longer. However the same case works fine on my Windows 7 installation.
I assume that the installation of .NET 4.5 has replaced the control templates for my standard controls. Therefore I cannot create copies any longer.
Ironically, it seems Mono supports much of the .NET 4.5 functionality, and that it can be installed on Windows XP.
If your need C# 5.0's async and your client refuses to upgrade it's OS, this can be an option.
I have run into some serious issues developing .NET programs for 4.0 against computers with 4.5 installed. One issue, for instance, is that if you are doing WPF development and have a private setter on a property - if you're binding to that property with Mode=TwoWay, you will not get an exception if you're developing against .NET 4.5! You should get an exception and you will if you're in an environment with only .NET 4.0 installed (even though you're developing to target 4.0 in Visual Studio). Now obviously you should not have Mode=TwoWay and a private setter, but maybe you had originally intended for the property to be only OneWay. The point is that this is just one of many examples of issues that are simply swept under the rug by 4.5 and has caused me to go back to developing in Windows 7 with Visual Studio 2010 and .NET 4.0 for anything targeting .NET 4.0.
In the meantime I have found a great blog of Scot Hanselman which answers my concerns: http://www.hanselman.com/blog/NETVersioningAndMultiTargetingNET45IsAnInplaceUpgradeToNET40.aspx
.NET 4.5 is an in-place-upgrade and replaces the .NET 4.0 CLR, but it will still be possible to create .NET 4.0 applications with Visual Studio 2012.
EDIT: I now installed the final release of VS2012. My existing .NET 4.0 projects compile and run, no problems so far. The only drawback is, it doesn't support Windows Installer Projects any longer. You can switch forward and backward between VS2010 and VS2012.
BIG EDIT: We should wait until Microsoft announces the final decision, it's not clear yet, only conclusions.
But, I think that Microsoft won't drop support for XP and Vista that easy, it appears that the matter of decreasing support is just for speed-purposes to show it to the developers.
Also, if the it comes true and Microsoft Stopped the support for XP and Vista, then you have the virtual machine as an excellent choice!
Best wishes
Well, the title says it.
Is it possible to create a service on Windows Embedded CE 6.0?
I could not find a detailed information.
Services run in the servicesd.exe context. Documentation between versions seems patchy; documentation for CE 4.2 can be found here, and for CE 7 here and there is an example here for 5.0. There are CE 6.0 specific articles here and here that may help with any differences from earlier versions, but you may find the 7.0 documentation applies.