Use Angular with an existing Asp.Net Website [closed] - c#

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
I am working on a project where we already have an existing website built using Asp.Net. We are planning to add some new pages and update some existing one.
I am planning to develop those new pages in Angular 5 with Webpack. We can not convert the whole website into Angular due to budget constraint but ultimate goal is to convert in completely in Angular 5.
Have anyone worked on such a hybrid app in recent future?
Can someone please throw some light on it, whether it is workable and If there is any performance impact due to mixing up the technologies.

Yes I'm working in a similar situation, and it's definitely possible. An .NET page (MVC?) can return an Angular SPA and take control of the UI flow from that point on.
Say you want to start by creating a "User Profile" page in Angular. When the user navigates to that page in your standard MVC site, it should return the page with the Angular application loaded (as a javascript script reference). From there on, the Angular app can handle further redirects and logic.
It does make some things complicated, but it's usually not feasible to port things in one go. This approach has allowed us to move over to Angular, 1 page at a time.

We at a large company have done exactly that. It is very simple. Using angular-cli create a new project
ng new my-project
and copy the contents into the root of your existing ASP.NET solution. You will now need to use
ng build --watch
instead of
ng serve
and copy the script includes from /dist/index.html into your aspx or cshtml file.

Related

Using angular 4 for making just ajax call [closed]

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 5 years ago.
Improve this question
I want to use Angular 4 for doing small operation like just making ajax call. Note: I know, I can use plain jquery to do this... blah... blah...
Question:
What Angular 4 Nuget Packages I need to Install for doing small operations like just making ajax call. Any example will help.
Technologies I am working with: Asp.net MVC, .Net Core, C-Sharp
This would be an inappropriate use of Angular. Angular is a client-side technology whose primary purpose is to provide a single-page application (or SPA) user interface for a Web application.
The idea is that the entire application runs on the client and does not require going back to the server to navigate between the pages of the application. The only time an Angular application needs to hit the server is to get data or to lazy load more of the application.
It makes no sense to use Angular within an MVC application to retrieve data.

Configure WebClient to speed up download [closed]

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!

Getting my feet wet with asp.net mvc - I'm feeling a bit overwhelmed what to choose [closed]

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 a fellow winform/wpf dev. Everything seems to move into the web atm.
Well I've got php and html5/css3 experience, but asp.net seems not that straight forward.
With the upcoming asp.net vNext I'm confused which technology to choose. To get into it,
I've decided to do a simple ass-hat youtube online converter.
On the one side people claim to choose always the best and latest ones, but on the other side
they are not.
Does it even matter? Is vNext that different from what we got today?
I'm sorry to ask such a "simple" question, but in the past no one told me to choose wpf.. you can imagine what happened :)
I'm a huge fan of telerik. Is telerik the to go suite for asp.net?
ASP.NET vNext is still in preview. For someone new to ASP.NET I would recommend looking at Get Started with ASP.NET. For a "standard" website I would recommend ASP.NET MVC, and for a SPA-like application using e.g. AngularJS I would recommend ASP.NET Web API.
I would recommend going with a stable version choose the latest ASP.NET MVC 5 , you can always find simple and informative tutorials on ASP.NET MVC, and yes , telerik is one among the best 3rd part controls, which you can easily integrate with asp.net mvc.
If you are going for more pure web development, you can choose asp.net web api to host service as http and consume them using jquery ajax and several other clients

the best way to build a Business Application in .NET [closed]

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.

Static pages (.html) vs ASP.NET pages (.aspx) [closed]

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
we are going to develop a media website where we will show current news.
For that we have 2 strategies:
Create window service in C# which will generate static (.html) pages for website (with updated news) as there will be only images and text (no postback or server-side event required) on website and then service will upload affected pages on server.
Create application in ASP.NET (.NET Framework 4.0) and use output caching for few minutes in it (as news updates in every 2-3 minutes).
Please suggest which one from above will be more preferable from performance (or other) point of view in my situation.
Please also suggest if any other strategy may provide me better solution. Thanks.
Making static pages will also prevents user to wait until new page is generated on server,so there is no way,only html can understand either new page or itself is generated again.This will cause user to make an interaction with the page (refresh) to find new results,so the cycle ends.You cannot expect user to know when content is changed.
As long as the content is dynamic in time interval,you should prefer asp.net solution with AJAX requests.You can make this with single page.
DO NOT FORGET that either developing via HTML or aspx or any kind will display your results in HTML output,so unless your page shall use any server content,try asp.net dynamically.
I can also assist code,please verify the specs.
Best Regards
Second one will be nice method
Problem with the first method:
HTML page want to be created each time
Created HTML pages what to be deleted or overwritten each time
Whole page want to be recreated (by using AJAX update can be done faster)
so comparatively second one is the right method.

Categories

Resources