tag:blogger.com,1999:blog-8980734269859237005.post1202144400521711914..comments2024-01-30T01:03:21.768-08:00Comments on DevCurry: Adopting ASP.NET MVC enhancements in an Existing Web Forms ProjectSuprotim Agarwalhttp://www.blogger.com/profile/08349831623922214390noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-8980734269859237005.post-52689553126784215432015-03-18T17:08:31.141-07:002015-03-18T17:08:31.141-07:00Great article. Been needing to look into this due ...Great article. Been needing to look into this due to a Web Forms project that's older, but need to have new stuff added to it.<br /><br />Sadly, I got the following when trying to nav to my new Area.<br /><br />Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the Anonymoushttps://www.blogger.com/profile/14023480712758429391noreply@blogger.comtag:blogger.com,1999:blog-8980734269859237005.post-79080285655865858412013-06-01T02:50:25.835-07:002013-06-01T02:50:25.835-07:00@Tim
You can't mix languages in same project. ...@Tim<br />You can't mix languages in same project. You can add VB.NET MVC to VB.NET WebForms project.<br />But you mention Winforms project? That's a different world.Deefhttps://www.blogger.com/profile/15438887210095088532noreply@blogger.comtag:blogger.com,1999:blog-8980734269859237005.post-25722829609637995372013-05-23T06:24:14.302-07:002013-05-23T06:24:14.302-07:00We have a large winforms vb project, I assume if w...We have a large winforms vb project, I assume if we followed this methodology we couldnt use c# MVC?<br /><br />Cheers<br />TimTimhttps://www.blogger.com/profile/16665287570678404441noreply@blogger.comtag:blogger.com,1999:blog-8980734269859237005.post-17247610244248402412013-05-18T08:16:37.921-07:002013-05-18T08:16:37.921-07:00I was asking for the second case, thank you for yo...I was asking for the second case, thank you for your answer!Tasos Khttp://codingstill.com/noreply@blogger.comtag:blogger.com,1999:blog-8980734269859237005.post-72967845745241006592013-05-17T09:03:50.471-07:002013-05-17T09:03:50.471-07:00@Tasos: Your question is subjective and depends on...@Tasos: Your question is subjective and depends on many factors. If you want a plain comparison in what gives better performance between WebForms and MVC, then MVC takes the prize (one reason being there's no viewstate, second its closer to HTTP)<br /><br />If you mean adding MVC to an existing WebForm application may slow things down, then my answer is No. If you feel the performance has Suprotim Agarwalhttps://www.blogger.com/profile/08349831623922214390noreply@blogger.comtag:blogger.com,1999:blog-8980734269859237005.post-17558637742569191362013-05-16T23:21:11.736-07:002013-05-16T23:21:11.736-07:00Very nice concept! I will surely look into it sinc...Very nice concept! I will surely look into it since we have a few Web Forms projects that cannot simply be converted to MVC. <br /><br />I would like to ask if you noticed any performance issues when this application is in production? <br /><br />Loading both Web Forms and MVC modules could lead to a less fast application?Tasos Khttp://codingstill.com/noreply@blogger.com