I like to know the difference between Asp.net and Java EE.
J2EE (since 3 years to be called "Java EE") is a bit broader than ASP.NET (that was an understatement). You can best compare "ASP.NET" with "JSF". They both have the same purposes/capabilities: a component based MVC framework which offers taglibs which are to be used in respectively ASP and JSP pages. The major difference is that ASP.NET is to be runt with C# "codebehind", while JSF is to be runt with Java "codebehind".
That's basically all. The one is based on C#, the other is based on Java.
Java and .NET? ahem
You would love working on Java EE ;)
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 heard there is a port of spring framework to .Net framework which is called spring.net.
Anyone can compare those two frameworks? If design the system, which one is prefered or both can be used.
Spring is for Java, Spring.NET is a .NET port of the Java framework.
See the overview page for a summary of the modules it implements.
You can't use both since they are written for different platforms. If you're designing the system and have the freedom to choose which platform you're implementing in, you can choose either Spring for a Java implementation or Spring.NET for a .NET implementation.
They are slowly getting a bit different, especially with the support for .NET specific things, such as WCF.
If you're going to decide to implement in .NET/Java I would take more into account than simple Spring/Spring.NET.
Spring is the original Java version and Spring.NET is a .NET version. Spring is better, as the .NET port is not as good as the original. For .NET, you are better of with Castle Windsor. The best thing is to use none of the dependency injection containers because dependency injection is not a good design pattern to follow. Neither is MVC. Java has many differences from .NET. .NET has advantage of Web Forms over Java. If you are using .NET, use the best UI platform which is Web Forms. If you are using Java use JSF.
I am developing web application using asp.net, but i want to work on asp i have to install asp or can we write the code using asp.net, what is the main difference between these two asp,asp.net. Thank you
ASP is the legacy version of active server pages that was created before the .NET framework. It works on IIS and is written in VBScript or Javascript.
ASP.NET is the newer version built on top of the .NET framework and is written in VB.NET or C#
IMO, you should spend your time learning and using ASP.NET as classic ASP is rather ancient in terms of web technologies and will likely not be supported for much longer (merely guessing there..)
You may also want to consider looking at ASP.NET MVC as a possible solution as well.
You should be able to use classic ASP in a .NET environment running IIS. If that is what you're asking.
Does anyone know about any articles/examples of using System.AddIn with ASP.NET and/or ASP.NET MVC applications?
I'm looking to use System.AddIn to make an ASP.NET MVC application extensible.
The examples I have seen all use the Managed Extensibility Framework.
The Managed Extensibility Framework
(MEF) is a new library in .NET that
enables greater reuse of applications
and components. Using MEF, .NET
applications can make the shift from
being statically compiled to
dynamically composed.
See also Choosing between MEF and MAF (System.AddIn)
I've just started working on an ASP.NET project which I hope to open source once it gets to a suitable stage. It's basically going to be a library that can be used by existing websites. My preference is to support ASP.NET 2.0 through 3.5, but I wondered how many people I would be leaving out by not supporting ASP.NET 1.1? More specifically, how many people are there still using ASP.NET 1.1 for whom ASP.NET 2.0/3.5 is not an option? If upgrading your server is not an option for you, why not?
Increasingly I think not.
The kind of large rigid organisation currently still clinging to 1.1 (probably because they're only just upgraded to it) is also the kind that's highly unlikely to look at open source solutions.
If I were starting a new ASP.Net project right now I'd stick with .Net 3.5 and probably the new MVC previews.
Remember that .NET 1.1 is going out of general support in October of this year (and that includes ASP.NET 1.1).
I think you would be perfectly fine with targeting just 2.0 and above, someone who would use your library would most likely be doing new development and using at least ASP.NET 2.0. I think it would be a very small group of people doing new development in 1.1.