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 8 years ago.
Improve this question
We are building a new Business Application using .NET technologies. First we started looking at some Javascript frameworks as we are basically converting a windows app to a web app so we thought using JS would give the same user experience as win forms.
We looked at many including Angular (no rich controls), KendoUI and WIJMO but ended up writing lots of JS and our prototype project became complicated as we used the SPA (Single page application) approach.
Is there is a way to get the simplicity of ASP.NET MVC and the great user experience of JS frameworks? Has anyone had any experience with building a Business Application? What are the recommendations?
Thanks
Yes, we use a mixture of these technologies and a simple eventing strategy for communication between the server/client
SignalR - for a persistent event pipe (transport)
Angular - DOM manipulation/data binding
Bootstrap - Great starting point.
MVC - awesome asset pipe-lining in .net, allows for the bundling of lots of js files into one, and partials allow for sane management of a very componentized page structure.
TypeScript - at scale js is very hard to maintain, refactor and debug, typescript removes an entire class of run-time errors and allows for very good code completion and refactoring tools in Visual Studio with ReSharper.
Look into Ext JS from Sencha.
Ext JS uses an MVC architecture and has a whole bunch of nice user interface widgets.
Disclaimer: I am not affiliated with Sencha in any way. My company, however, does use their framework in our applications.
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 4 years ago.
Improve this question
The project is directed to provide finance based solutions (specially concerning stocks).
for back end the technologies i am planning to learn and use are web C# based web API and SQL server for database. which is best to use as a webAPI asp.net or core or mvc for my api?
bonus questions: since i am learning these technologies, is it better to learn a cross platform based frameworks like react-native and xamarin. and which do you think is best platform that generates mobile apps in addition to windows application, if performance is a key factor?
To answer your first question, WinForm is much simpler than WPF to learn, but WPF is way more powerful and flexible (in my opinion). So I suggest to start directly by learning WPF.
CrossPlatform frameworks like xamarin are good way to rapidly deploy solutions in all platforms. But, if you're creating custom views, you'll have to create a custom view for each platform anyway.
Xamarin.Forms (cross-platform) is much slower than using the native language of each platform.
Last thing, if you want to deploy your app for Windows + Android + iOS, you should use Xamarin.Forms, it's pretty similar to WPF and it gives you some UI elements to share with each platform (Labels, Switchs, StackLayout, ...) and all the libraries that C# can give you, while it stays outside of native code.
Hope this helps,
All the best.
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 8 years ago.
Improve this question
What I am doing
I am trying to migrate Classic Asp app to ASP.NET MVC. Classic App was written for 15 years. There are no chance to write new project and migrate all code at one moment. Business app must work 24/7.
What solutions I have found
I did not find any good solution. One advice I have found starts with words "I feel your pain, bro". Business can not give such human resources for global refactoring. So the only way I found is to write some kind of proxy using WebClient.
Architecture
I have server with IIS that hosts Classic ASP app. I will add MVC app near it. Every request received by server will be managed by MVC project. If there is action that request asks - MVC app will work as normal. Render view, return to client. If there is no such action Controller will call Classic ASP by using HandleUnknownAction method.
So it will do some work by processing url and cookies and in the end call Classic Asp app by WebClient.DownloadString(). The return string (HTML response) it will embed as content to the page (Headers, Footers are in MVC Layout). Need to mention - project is not highlighted but near it.
So I can migrate old code by small pieces. Action by action with no impact on application. Just by creating action methods in MVC.
Requirements
Response time will grow significantly.
There are no alternatives.
Question
I want to know every possible chance to speed up such web app. Maybe by tweaking WebClient configuration or so. Are there any settings to do this? Maybe some advices to manage webclient pool? I do not need to make cross server requests - does this open any abilities? Maybe this is the place for async calls? Or reorganize server structure?
Thanks for any advice!
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 4 years ago.
Improve this question
Some background: We have 3 websites that are all part of a standard workflow. Each website handles a different part of the workflow.
Website 1 is for sales (pricing, sales, etc)
Website 2 is for engineers (implementation, coding, testing)
Website 3 is for reporting (used by all but primarily for administration and management)
We're gearing up to add notifications in a way that's a lot like how StackOverflow does notifications. I actually posted this on Meta Stackoverflow because that seemed like the best route, but the question didn't get very far. The notifications in our context would be things like "John Smith's timesheet is late" or "You have been assigned to a project"
Now I'm curious as to how other developers have set this up. I'm primarily worried about code repetition and maintenance at this stage.
Specifically, should each website be responsible for implementing its own notification client? That seems like it'd be really easy for code bases to get out of sync. But at the same time, even if you build a library you still need to handle the HTML templates somehow. How much duplication of functionality is acceptable? I'm at a loss here.
As you can tell, I'm not really sure where to start. If this were for a single website it'd be a different story, but implementing it across multiple websites at the same time has be puzzled.
Some miscellaneous facts about our stack:
Server side: ASP.NET MVC 4 (C#)
Cliebnt side: jQuery + Knockout
Database side: SQL Server w/ LINQ to SQL
IE not supported.
You can also do something like google +1 button. Link to a javascript common to everybody and have a custom html tag that will indicate where to put the data with configuration if needed.
Since you own all the websites, you can put everything in it's own .dll and add it to the solution of each solution.
Are you need something like Redis.io? There is Publish-subscribe in Redis.io.
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 9 years ago.
Improve this question
I'll soon be looking into writing a small business workflow application that I'd like my userbase to use across all devices - iOS Tablet, Windows PC, Windows Tablet, Mac, Android Tablet are the key targets.
I'm fairly new to the 'app' dev space and I don't know much about what frameworks and industry standards are forming around PC and mobile friendly applications, if any?
I'll be writing the core of the application in C# and I'm looking for technologies (HTML5, JS, etc) and even frameworks (I saw Xamarin might be okay?) that implement the View of the application. The tighter its tied to C# the better it'll be for me and the cleaner the transition between my chosen platforms the better.
I just created one using Jquery Mobile, and an odata C# webservice. Its just what work wanted me to but I see the framework being used alot. So pretty much get the data with the webservice then use javascript and html5 to display it.
If you want to write your application in C#, and not implement it as a web service, then I think the only option is Xamarin for the iOS / Android platforms (and .NET / Mono on Windows / OS X).
This does not mean using a single technology for the View, though, as Xamarin UI code is not portable across iOS and Android (this has pros and cons involving the age-old native feel versus shared UI debate).
If you are flexible on implementing it as a web service, then your server logic can be written in C#, with a shared HTML 5 client across all platforms.
If you are flexible on using C#, then you have more options outside the scope of this question.
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.