Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I'm about to develop an ASP.NET Mvc website for a startup. I've never done this before, so i have few architecture/infrastructure asks.
1/ Is it reasonable to develop the website in Asp.NET Core MVC ? I've read several times that the technology may not be mature for the next 1-2 years.
2/ In a first time, i'll have a low budget. Knowing this, would it be possible to use TFS ? IIS ? Sql Server ? If it is too expansive, which are the alternatives ?
3/ Should i host the website using Microsoft Azure ?
Thanks for your help.
I can share my own experience on this matter. The definite answer is yes.
Yes, it is reasonable. You have mentioned it would be a startup, so you are fortunate to try latest technologies. Microsoft has actually released .NET Core and they are offering long term support for the release. Microsoft takes LTS seriously. I am using ASP Core from early beta and although there were some problems back then, it is quite stable now.
TFS, IIS and SQL Server are different products for different purposes. Thankfully, you do not have to stick with Microsoft stack entirely. I am using PostgresSQL (with Entity Framework), Kestrel + NGINX on Linux (Ubuntu 16) and Git (gitlab). All of them are stable, open source and no worse than Microsoft solutions.
In my personal experience Azure is great but too expensive. That was the main reason I tried moving to .NET Core instead of Windows only - I wanted to host it elsewhere. Given that the ASP Core is released, you have at least two options. You can self host (what I do) get cheap VPS from Google/DigitalOcean/Amazon/..., install ASP Core (or Docker) and be happy. This way is cheap, and you are in full control, but it requires some Linux Administration skills. The other way is to find non-Azure ASP hosting, like SmarterASP (just an example, not ad) and publish your product right from the Visual Studio.
To sum up, yes it is reasonable to build your app on ASP Core.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I'm a PHP/JS developer, now I have a proposition of making a project based on C#, which would then work on a Windows server.
I have no experience with either (C# or Windows server) but I was given some time to learn it, if we agree on the details.
The project is about an API (web service, RESTful).
And now I have two questions - I haven't touched Windows for about 10 years, so:
Am I right that I have to learn C# and the .NET framework? Is the .NET some sort of standard on MS servers?
Is this reasonable to work on the project using Linux machine as the work environment and then upload it to the Windows test server for testing?
BTW, right now the project is very simple, probably only a few classes. If I'll make it, I can later install Windows on my workspace, but for this very small project, where time allowed for the implementation is about one day (excluding my learning process) I would prefer to avoid it.
C# is a programming language, .NET is a framework. There is an old .NET Framework that is windows only and the newer .NET Core (the newest version is called just .NET 5), which is cross-platform.
You can develop .NET core apps on linux as well. Note that you won't be able to use Visual Studio (IDE), which is only available for Windows and Mac.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I started using .Net when it first came out 15 years ago (v1.0). My last experience was writing an enterprise-wide API in 2018 using Web API.
I've been focusing in React and Azure since then. What is the latest and greatest way to write web services in .Net now? Is it still "Web API"? Or is there a new preferred way to write web services on .Net Core 3.0 that I should learn?
I see a lot more job postings for .Net Core now. It seems like a lot more companies have bought into .Net core at this point. Has Microsoft announced an end of support date for .Net standard?
Are there any new framework features or language syntax that I should be familiar with?
There's just ASP.NET Core now. You can create API-style controllers or MVC-style controllers/views (or Razor Pages, Blazor, etc.) all in the same project. There's templates for things like an API, but this just gives you a starter; it doesn't confine you to one approach or another.
In general ASP.NET Web Api was just about REST-style applications; ASP.NET Core has the same thing. However, it also supports gRPC and OData, and can be made to work with GraphQL. Any of these can be used to create "web services".
.NET Standard is an abstraction, not a framework. Each successive version of the .NET Standard gains a wider API footprint, encompassing more of the .NET frameworks (.NET Framework proper, but also Unity, Xamarin, Mono, and .NET Core) under its umbrella. .NET Standard isn't going anywhere, per se. However, .NET Core is gaining more an more features from .NET Framework, and has basically already surpassed it. The next major version of .NET Core will actually be ".NET 5". .NET Framework will go away (though still be supported by Microsoft for legacy apps), and Unity, Xamarin, and Mono APIs will be rolled in, to create one .NET to rule them all. Long and short, yes, .NET Core should be your focus.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
I have a .net 2 Core web app on windows IIS. No issues with the web app. How can I successfully run:
1) a .net core console app;and
2) a regular windows executable?
The console app is needed because of the work passed to it can take several minutes - sometimes up to 10 minutes to complete. Probably too long to expect a user to keep their browser open.
I have tried using "System.Diagnostics.Process" on the windows app with much success. I figured before I started trying with the Core app, I would get some suggestions. Let me know if any additional information is needed.
Console app in .net core 2 has a lot of new features in it, explaining it in a nutshell is a little bit complicated.
I would suggest starting from this
guide
on git hub which sums it up really good.
I would also recommend looking into this post regarding Windows Executable (which is about .net core 1.0 but is more or less the same) and this article.
Those will be a good place for you to start.
I'm not sure if this will be useful, But you can try the task scheduler to call the app. Gets rid of a lot of permission problems.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am a C# .NET developer, and the tools I use to build a web application are:
SQL Server
Entity Framework
.NET Web API
ASP.NET MVC
HTML/CSS/jQuery
I have been reading up on AngularJS, NodeJS, MongoDB, and ExpressJS, and it certainly seems like with these "Javascript-ish" technologies, you can build a full blown web application.
My question is where does this leave me with my knowledge of the .NET stack? I want to start embracing these newer technologies, and build my next website with them, however, I am confused as to whether I should completely do away with the .NET stack, or if I should complement these newer technologies with the power of the .NET stack where it might make sense. Here are some of my thoughts:
MongoDB could replace SQL Server and Entity Framework
AngularJS can pretty much replace ASP.NET MVC (since both are MVC patterns, having both would be redundant, I think)
But when it comes to building an API layer, would NodeJS completely replace ASP.NET Web API? or could I use them together? What would make the most sense (generally speaking)? Considering that NoSQL databases like MongoDB have javascript-like syntaxes, do we even need server side APIs? Couldn't the client (theoretically) directly talk to the DB?
And where does ExpressJS fit in?
I am hoping someone can help to clarify how these technologies fit in with each other. Pretty sure that a lot of .NET developers looking to explore these newer technologies have the same questions.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I`m learning programming languages. And I decide that I need to lear a new web framework. I have 2 candidates: Django or ASP.NET MVC 2.
Can you say me the difference between them and what is so interesting?
Try both, then decide.
Well, I'm using both and found both to be state of the art, easy to learn, fast and easy to install.
Maybe don't look at it from a technical standpoint but from the context. ASP.NET needs a Windows Server, ASP.NET and an IIS installed. You have the license for that? Django on the other hand is open source runs on cheap but fast linux machines and provides you with the Python Language and it's vast easy to install moduls.
If you don't know Python or C# maybe Django is the better way to go. Djangos Documentation is great and has a great tutorial, which is yet to be found on the ASP.NET MVC side.
Well, the conclusion is: Try both :) And if you're gonna use ASP.NET MVC, watch the Nerddinner Sessions (PDC) by Scott Hanselman and Phil Haack.
I would create a small app to try each for a day or two and then choose.
I can't speak for Django, but here are some Asp.Net MVC benefits
Tight integration with other Microsoft technologies
Uses jquery out of the box
Choice of several server-side languages
Very flexible (choice of unit test framework, view engine, model architecture etc)
and a potential negative
Might take extra work getting it running on anything other than Windows
What reasons lead you to choose those
two frameworks?
What reasons lead you to choose those
two languages?
If you don't like the answers, then keep looking. Otherwise...
Do you want to be on a
non-Microsoft web stack? Go Django.
Do you want to interface with lots of other
Microsoft web stack technologies? Go
MVC.
Do you want complied language speed? Go C#.
Do you want interpreted language portability? Go Python.