As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
A colleague of mine ran a simple load test using VS2010 on a Webforms project and an Asp.net MVC project and noticed that Webforms was serving around 83 requests per second whereas Asp.net MVC was serving 28 requests per second. Both the sites were published on the same server with similar settings.
Webforms project had 10 pages 5 of them displayed simple text messages using labels and the other 5 had text box controls. Similar functionality was built into the Asp.net MVC site so that the output is the same as the Webforms pages. Tests were run with both constant load and incremental load with similar results.
I am a little surprised with the results. Does anyone know why MVC is slower that Webforms?
Thanks!
Hmm. Without much info to go on, perhaps you should instrument your code to see what's taking a while and/or the difference between Web Forms and MVC.
You might use some aspect oriented programming techniques to remove the burden of all those logging commands.
Here's one such framework:
http://code.google.com/p/postsharp-user-plugins/wiki/Log4PostSharp
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I want to develop a personal blogging website using ASP.NET MVC 4.
I know that I could be using WordPress/ Joomla/ Orchard/ Umbraco/ Funnelweb, etc., instead of reinventing the wheel but I really wish to try it out myself.
I do not want my website to look like some beatle-aged archaic remain. I see plugins like Akismet/ Prettify/ Markdown/ nrelate that add amazing functionalities to your blog. But I am not really sure if I would be able to use any of these in my custom application as most of them are PHP based. I want to stick under the Microsoft roof and implement technologies like HTML5, CSS3 Silverlight5 and WCF 4.0, along with ASP.NET MVC 4. (At least thats what I plan to do)
I understand that I need to develop a scalable database design that could accomodate newer functionalities in the future. Additionally, the exorbitant focus on SEO and cross-browser capabilities is overwhelming. Permanent links for individual blogs, internal navigation, video-embedding inside posts, etc., sound like building Rome in a day
Please if you could guide me personally or direct me to appropriate resources, it would be very helpful.
I am sort of doing it right now on my own. It's not done yet but it will give you an idea: MvcBloggy.
Also, have a look at FunnelWeb source code. It's written in C# and uses ASP.NET MVC 3 I believe but it's a really good resource and easy to follow.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have worked with ASP.NET webforms and windows application with C# but due to the change in nature of my job, I did not work with ASP.NET at all for 2 years. Now, I want to come back to ASP.NET and MVC is already there. I am following the tutorials on www.asp.net.
Should I learn LINQ and EntityFramework to learn MVC? Are there any other fundamental things to learn before learning MVC?
Do yourself a favor and learn HTTP, then you'll be good with any framework.
Now, I want to come back to ASP.NET and MVC is already there
Nevermind! Get started with MVC!
Should I learn LINQ and EntityFramework to learn MVC?
That is not necessarily a prerequisite. Maybe you need get used to lambdas (as they are used by many methods in MVC), so learning LINQ will guide through that.
Get a good understand of AJAX and jQuery (as it's included in the MVC stack) and you're good to go!
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I know many have asked the MVC vs Webforms question many times. My question is slightly different in that I am currently updating my skills from ASP.NET2/VB.NET to ASP.NET4/C#. I am seriously thinking that I should perhaps not waste time in upgrading my Webforms skills which are Okish, but instead put the effort into starting again with MVC. I keep looking at all the properties of ASP.NET server controls and sigh !!! I do see the benefit in just focussing on web technologies such as JS, CSS and now JQuery and CSS3.
I would be interested in your thoughts?
It sounds like you are doing a clean-slate here. You are changing languages and technologies. My advice would be to identify what you feel is the best technology going forward and learn that. You are already committing to learning something new - make it the most valuable experience you can make it.
From my perspective, I would recommend MVC. Personally I feel that this is the better platform to move forward on. You will have to add quite a few auxiliary skills such as Razor, JQuery and all the rest but it will be worth it. The bottom line though is that it is what is best for you. If your environment is better served by Webforms, then that is the best choice for you.
Six months ago I changed jobs. I was previously working at a large company that was still on .NET 2.0, VB.NET and ASP.NET WebForms. I now work at a company that uses .NET 4.0, C# and ASP.NET MVC3. So, I've been through this myself.
If you understand how the web works and want complete control over the client experience, MVC is the answer without a doubt. At my previous job I would end up pulling my hair out because I hated how WebForms prevented me from creating a page with clean markup. But, a lot of people don't know how HTTP, CSS, Javascript and HTML all fit together. WebForms was a solution to that. But, it's much more fun and performant to have complete control of what you sent to your customer/client.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I need to add a real time dashboard of data to a ASP.NET MVC application. The dashboard needs to be refreshed every few minutes from SQL server 2008. I was going to use ASP.NET MVC, with jQuery and AJAX. But Silverlight 3 is a possible option (each client has Silverlight 3 installed). I know WPF, is it worth the jump to SL 3 for this?
A dashboard is an excellent use of Silverlight. You can create some terrific looking UIs and it can be used to create a very compelling visual experience. Charts and gauges will pop off the screen. Your data will look incredible.
There is a learning curve when developing your first Silverlight app so make sure that you're clear on what the final product will be. If the requirements are well defined, you'll be able to determine if you think it is something that you and your team will be able to achieve.
For a dashboard, I think a JQuery solution works best and that is the direction I would go in. I'm still a little unsold on the long term future of Silverlight compared to the AJAX/HTML 5 future.
I would only go to SL 3 under one of the 2 scenarios below.
You need a rich UI experience (ex. fancy charts, graphs, etc..) that WPF/SL will help you achieve easier. If the user interacts with the dashboard, then that makes it a good candidate
You want to learn SL 3 or want your team to learn SL 3
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We are looking to use the MVC Framework in our SP Application.
This is what we are trying to accomplish...
A virtual directory within the SPSite which can host and run MVC.
for e.g., /_layouts/MVC/
Any hints on the required configuration changes (if at all this is possible) will be very helpful.
This might be of interest to you
http://www.codeplex.com/SharePointMVC
I published it about 5 minutes ago.
It is basically a library to help rendering ASP.MVC inside a SharePoint masterpage.
Still early days but you get the idea.
You're going to have a hoot of a time de-inheriting everything (modules, handlers, assemblies, namespaces) in the MVC app's web.config. I would recommend that instead of trying to get MVC working inside of the same IIS web site, why not just run your app outside of SharePoint? Joel Oleson just blogged about using "widgets" or "web parts" as a form of SharePoint integration:
Joel Oleson
I have heard from the MS MVC team that there is no plans for Sharepoint to use MVC. However MVC can be used with Sharepoint with a few tweaks
The following sharepoint site, www.themedicinecabinet.co.uk, was built using ASP.net MVC 2.
This article explains how this was done
http://vspug.com/mbailey/files/2010/04/Using-ASP.NET-MVC-2-with-Sharepoint-Publishing.pdf
We've just released an opensource project that let's you use SharePoint 2010 as the backend of a site and use ASP.NET MVC3 on the frontend. We've been using the code base for the last two years and wanted to share it with the community since we're confident others would find it useful.
Documentation is still sparse - please feel free to reach out if you have any questions or need help.
http://www.slamcms.com
I would recommend running your virtual directory in it's own app pool. I'm leveraging MVC on some other Microsoft products and the app pool's Managed Pipeline Mode must = 'Integrated' for MVC.