Can we use vb.net lagnuage in MVC ASP.NET 2017 or latest version of Visual Studio 2017.
Yes. I see no reason why that wouldn't be possible.
In Visual Studio 2017 you have the options to create an ASP.NET MVC 5 / Web API project using Visual Basic as usual.
I'm unsure whether you'll be able to create ASP.NET Core / MVC 6 applications using VB.NET, since I havn't been able to find any sources confirming this. I reckon, though, that it should be possible, since VB.NET works perfectly fine with .NET Core.
Related
How can we create ASP.NET WebForm .NET 6 VS 2022 based ASPX pages (.aspx), not razor (.cshtml)?
You can't.
ASPX is from the WebForms (System.Web) part of the .NET Framework. This area was not ported to .NET Core, or to newer versions of .NET (5+), and there are no plans to do so.
For a component-based web development framework, Blazor is the new Microsoft platform. There is a migration guide here which can serve as a starting point, but migrating will be an involved process.
There is no way you can create WebForm project (with .aspx) in .NET 6.
You can use VS 2022 to create a WebForm project if you install .NET Framework 4.8.
In Visual Studio 2015, there are templates for asp.net 5 (start site) and asp.net 5 mvc. What is the difference between these two?
Webforms is supposed to be gone so asp.net 5 isn't webforms.
ASP.NET 5 is a new platform including the following features:
New flexible and cross-platform runtime
New modular HTTP request pipeline
Cloud-ready environment configuration
Unified programming model that combines MVC, Web API, and Web Pages
Ability to see changes without re-building the project
Side-by-side versioning of the .NET Framework
Ability to self-host or host on IIS
New tools in Visual Studio 2015
Open source in GitHub
ASP.NET MVC 5 is just the current stable version of the MVC framework based on ASP.NET 4.
I guess you are confusing it with the new ASP.NET MVC 6 which is part of ASP.NET 5.
So basically the template for ASP.NET MVC 5 in Visual Studio 2015 is there for backwards compatibility allowing you to still be able to create MVC applications on the old platform.
First of all its not a thing to compare.
ASP.NET 5 is the latest release of asp.net framework series with lot of new features. And ASp.net MVC is one approach (service/ framework) to develop web application(there are other approaches like web form and website). You can integrate MVC as a service to empty asp.net application and use.
ASP.NET 5 is cross platform also.
It is all packed in Visual studio 2015 where MVC templates are available.
I'm a little confused about one thing with version levels of various .NET software components related to ASP.NET MVC and the web api. Now I know VS2012 and .NET f/w 4.5 are going RTM "real soon now", but I don't want to make that up-transition for awhile (as in 6 months or longer). I am coding a new app right now whose initial incarnation (dictated by consulting client) has to be .NET f/w 4.0 and utilizing VS2010 (yes I know you can target downwards with VS2012 but that is not an option for me in this case - as a consultant you are sometimes dictated the tools/versions etc that you MUST use for a contract). So finally to the crux of my question - I just came across an article on MSDN by Mike Wasson, written in Jan/Feb 2012 timeframe, and it looks as if he used VS2010 and .NET f/w 4.0, but demonstrating the new-ish Web API technology utilizing ASP.NET MVC 4. So it IS possible to install the ASP.NET MVC 4 component within the context of .NET f/w 4.0 and VS2010, AND utilize the Web API component? Which, if that is true, I might want to do with this particular project rather than just using ASP.NET MVC 3 (and without using the Web API stuff at all), which is what i thought I would need to do. It's just that I thought to use ASP.NET MVC 4 and/or the Web API stuff, one HAD to use .NET f/w 4.5 RC and VS2012 RC prior to Sep 12 (or their RTMs after Sep 12). Is that not correct?
You can use mvc 4 and web api with .net 4.0. You cannot use features of .net 4.5 in it but all other will work.
So it IS possible to install the ASP.NET MVC 4 component within the
context of .NET f/w 4.0 and VS2010
Of course. It's RC at the time of this writing but you could download and install it from here: http://www.asp.net/mvc/mvc4 (Download the standalone installer executable for VS2010 from here: http://www.microsoft.com/en-us/download/details.aspx?id=29935)
Even when it hits RTM you will be able to use it with VS2010. Of course you won't be able to use .NET 4.5 speicic features with VS2010 though (things like async/await).
To reproduce the error I'm getting:
Create a new Visual Studio 2010 ASP.NET web site in Visual Basic, targeting .NET 2.0
Type "Public Property Test As String"
Observe "Visual Basic 9.0 does not support auto-implemented properties." error
Visual Studio 2010 is happy to use VB 10 against .NET 2.0-targeted Windows Forms applications, this only appears to be an issue with ASP.NET.
Is there a way to force Visual Studio 2010 to use VB 10 when targeting .NET 2.0?
No. A Web Site project is one that compiles within ASP.NET at runtime - as such, you've chosen to ask ASP.NET to run it as a .NET 2.0 project, so it will use the .NET 2.0 vbc Visual Basic compiler that's part of .NET. That compiler has no knowledge of VB 10, and so you're rightly being warned that it will not work.
The reason it can work for other project types is because the compilation is happening using a later compiler (usually the one built into Visual Studio).
I am working on re-factoring of an existing Asp.Net 2.0 web site. I am looking for a framework/pattern to modularise the application. As there is no WCSF for Visual Studio 2005 I can't use it and I also can not upgrade it to Visual Studio 2008 for reasons beyond my control.
I can use Mono-Rail but I would loose the existing controls functionality. Does any one know a good Framework/Pattern that can be used consistently across the modules on Asp.Net 2.0/Visual Studio 2005.
I came to know about Spring.Net Web Framework which supports Asp.Net 2.0 and Visual Studio 2005. It has few good features like Two way Model Binding, Navigation support, Validation and DI Container. Only problem with Spring.Net is huge Xml files to define everything