I worked in the past -- specifically back in 2008 to 2010-- with Silverlight applications within ASP.NET . Now in 2015 I need to develop a new 2D/3D graphical tool within ASP.NET, but I just read that Silverlight will be deprecated in the near future.
Does anyone know what is the next tool that will replace Silverlight for development of graphics and Computer-aided design in ASP.NET?
I believe silverlight is still a good option. The official end of life for Microsoft Silverlight version 5 is October 12, 2021. You have time. That isn't 'too near' really. If you are to create desktop application, you can then think of using WPF. Your silverlight experience would also help you with that and it is a pretty mature technology.
Related
We are going to create new application using Web Forms and we want to know when Web Forms (ASPX pages) Technology going to be obsolete or not be supported from Microsoft.
https://dotnet.microsoft.com/platform/support/policy/aspnet
So WebForms is part of .Net Framework.
https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies
“.NET Framework 4.8 is the last version of .NET Framework. .NET Framework is serviced monthly with security and reliability bug fixes. .NET Framework will continue to be included with Windows, with no plans to remove it. You don't need to migrate your .NET Framework apps, but for new development, use .NET 5 or later.”
So it's baked into Windows at this point if you want to use it. Everyone will discourage you from using it, as you are essentially mastering out-of-vogue and increasingly obsolete technology, and maybe not doing your career any favors. But if, like me, you have some huge WebForms app for which there is no time nor money to rewrite, then you can at least rest assured that it will continue to run on Windows.
Microsoft will be continuing to support ASP.Net WebForms for some time to come since much of it's functionality is based into the core .Net Framework. There are several locations to get information on which ASP.Net features/technologies such as ASP.Net MVC 4 will be going out of support soon. https://www.asp.net/support lists many of the technologies. For ASP.Net Webforms, it's tied to the Framework versions as best as I understand. https://support.microsoft.com/en-us/lifecycle/search?alpha=.net%20framework
Support policy for ASP.NET is documented here: https://dotnet.microsoft.com/platform/support/policy/aspnet
I need to get any ideas of how i should be managing our previous asp.net MVC 5.2 web application.. now i am using asp.net mvc-5.2 with entity framework 6.0. and i want to start phase-2 for some of these projects. so should i consider upgrading my mvc 5.2 to be using mvc6 (vnext) first ? and will there be any migration plans ?
second question , when is it expected for vnext to be released? or it is has been officially released ?
third question, will i be able to create a vnext project inside VS 2012 ?
I would simply recommend following the standard best practice of n-tier architecture and keeping logic related to things like querying a database in class libraries. MVC 6 is drastically different from previous versions, so there's no easy migration. You'll basically need to start a brand new project and move over relevant code where you can and spend a good bit of time converting code. For example, child actions are gone and have been replaced with view components. You'll need to go through any child actions you're using currently and create view components out of them. As I said, making sure your current MVC project is as thin as possible (by factoring out code into class libraries and such) will go a long way in reducing the amount of code you need to move/change.
As far as I'm aware, no release date has been set, but at least in the alpha and beta phases of Visual Studio 2015 and ASP.NET 5/MVC 6, Windows 10 has been required, so there won't be an official release likely until Windows 10 is public. However, Visual Studio 2015 has reached release cadidate stage, so I'd say it's definitely close, either launching alongside Windows 10 or shortly after.
Kind of answered this in point 2, but ASP.NET 5/MVC 6 will require VS2015. As far as I'm aware, there's no plans to add support to lesser versions. A lot of that has to do with Rosyln, the new .NET compiler. Trying to bootstrap previous versions of VS with support for an entirely new compiler/syntax engine would be a monstrous task. However, VS has been on an MSDN subscription model for many versions now and as long as you're a current subscriber you can always download the latest version for free. If you're not an MSDN subscriber, you can still download the community edition of VS 2015 for free. It's missing a lot of the more advanced VS features, but it's still totally sufficient for web development work.
I've heard rummors that ASP.NET 5 does not support VB.net. Is this correct? Or does this apply only on some particular scenarios?
Update 5/1/2015
On April 23rd, the ASP.NET team announced that support for Visual Basic will be coming to ASP.NET 5.
More information is on the .NET Web Development and Tools Blog: http://blogs.msdn.com/b/webdev/archive/2015/04/23/making-it-better-asp-net-with-visual-basic-14.aspx
Original Answer
Though it was mentioned in a comment, it's worth having a full answer.
There are no plans to support VB in ASP.NET 5 in terms of compilation, project templates, and other tools. This is discussed in the following GitHub issue on the ASP.NET 5 project: https://github.com/aspnet/Home/issues/236
As that issues also mentions, ASP.NET 5 has some in-progress support to enable non-C# compilers to be used, but there is still no official plans to support VB (you'd have to roll your own).
"We are excited today to announce that ASP.NET 5 will have full support with Visual Basic (both tooling and runtime – including cross platform runtime support). As always, we will continue this development of ASP.NET 5 in the open, and you can track our progress or even contribute on GitHub at http://github.com/aspnet/home."
Taken from:
http://blogs.msdn.com/b/webdev/archive/2015/04/23/making-it-better-asp-net-with-visual-basic-14.aspx
As per my understanding You can still develop application using VB.NEt in Visual studio 2015, but you will not get the benefits of ASP.NET 5 like cross platform etc.
This is my understanding. Official decelerations are yet to come.
i already built some web applications using asp.net MVC 3 and they work well, and currently i am in the state of starting a new web application for a medical clinic ; but i need to have some advice if i should consider using asp.net MVC 4 beta version instead of asp.net MVC 3?
thanks in advance for any help and suggestions ?
BR
Personally I would start in MVC3 and then upgrade the project to v4 when it's RTMd. Previous versions have had some issues when migrating from Betas (altho see update below).
You can be sure, however, that as with previous version increments, a swift and easy upgrade path will be available (usually there's a project conversion tool released at the same time).
I have a project I'm working on right now, and if I get to the web layer before v4 is finished, I'll be starting in v3 first.
I suppose it does depend, however, on whether any of the new features, such as the adaptive rendering via Mobile views (or indeed the Web API), are intrinsic to your solution. Just don't release on a beta platform :)
Update July 2012
I ended up getting to the web layer of my current project before v4 RTM so decided to go to the RC release first; then the nightly nuget packages for Web API support.
Apart from editor issues (that are documented), I've found no issues, even with integrating a whitelabelling extensibility library I've written, for MVCs 1-3, that operates at a very low level.
Would I have migrated early if I'd not needed the numerous benefits that the Web API provides? Probably not.
But as it is, I'm glad I did :-)
Unless you have a specific reason to use MVC 4 (perhaps a feature that isn't in MVC 3) I would stray away from using beta software for a customer/client. Who knows what bugs/issues you'll have to work around when developing the application or when you upgrade from beta to general release.
There's a reason it's in beta.
As Mackie says.. unless you need a specific feature in MVC4, i'd stay with MVC3. MVC4 is mostly just new features, and has very few changes in the way MVC itself works.
I disagree with Mackie in his comment about "there's a reason it's in beta", in fact MVC4 is very stable and has a go-live license to allow you to use it in production code. It's just that things may still change before final, which is tied more to VS11 than how stable it is.
For my thesis I want to develop an application in ASP.NET MVC, so a few weeks ago I had to make the same decision like you. This is my conclusion:
I should advice to use MVC3 (because it's stable) for your business projects.
There are some known issues ( http://www.asp.net/whitepapers/mvc4-release-notes#_Toc303253815 ) in MVC4 beta, so it would be a waste of time to get stuck one day because of beta problems.
When the time is there you'll be able to convert MVC3 with ease to MVC4. So don't hesitate and choose for MVC3 for now. You can decide later on if you want to upgrade or not.
At the link below you'll see how to easily upgrade from MVC3 to MVC4 at this moment: http://www.asp.net/whitepapers/mvc4-release-notes#_Toc303253806
We have a legacy system that uses both classic ASP and VB6/COM+, and are planning a migration to the .NET stack.
We are attempting to develop a migration schedule, and one key driving point will be "when will our old stuff stop working?".
For VB6/COM+, Microsoft has stated that it has no plans to include the VB6 runtime in versions of Windows after Windows 7 (yes I am aware that this is open to interpretation).
I have yet to find a similar statement for classic ASP. I have seen people reference the Microsoft end-of-life schedule for Windows 2008 Server R2 (which is sometime in 2018) and infer that:
(a) since classic ASP runs on Win2008R2 and
(b) Win2008R2 is good until 2018 then
(c) classic ASP is good until 2018.
Not sure I buy that, especially because we have contractual obligations to support new versions of Windows xx months after they come out, so staying on Win2008R2 as a solution is not an option.
Can anyone point me to something from Microsoft concerning end-of-life for classic ASP?
It will stay with us for some more years to come, according to this blog post:
Here's some interesting news from ScottGu and team. I was wondering what the lifecycle for ASP "Classic" was. I looked on the Microsoft Lifecycle page and didn't see it. I was fortunate enough to talk to ScottGu as well as Rich Ersek and was told:
Classic ASP is actually very much alive. It will ship again with Windows Vista and Windows Longhorn Server – so will be supported at least 10 years from that ship date. - ScottGu
and
Asp.DLL is part of VISTA so the runtime will continue to be supported based on the Vista support lifecycle.
All classic ASP development tools (i.e., Visual Interdev) are now in their extended support period and we will not be updating tools for classic ASP.
To get the best tooling/platform option ASP.NET is the way to go. - Rich Ersek
Windows Vista final release date as far as I've found is January 30, 2007 so it means classic ASP will be supported in new versions at least until 2017 and probably much further.
Scott Guthrie is Microsoft's Corporate Vice President, Server & Tools Business so he knows what he's talking about.
Edit: Finally (January 30th 2012) - official confirmation that classic ASP is going to stay with us for long years, including Windows 8:
The next major version of Internet Information Services (IIS) will be shipped as part of the Windows 8 operating system. The use of ASP pages will be supported on Windows 8 for a minimum of 10 years from the Windows 8 release date.
Here is a technet article on how to install on Windows Server 2012, so it should be supported for a long time...
http://technet.microsoft.com/en-us/library/hh831387
if you scroll to the properties section of that article it says it applies to Microsoft Active Server Pages 4.0. it doesn't say classic asp, or asp 1.0, or asp 1.1.
http://support.microsoft.com/kb/2669020