Eilon Lipton's Blog - All Comments

re: Migrating ASP.NET MVC 1.0 applications to ASP.NET MVC 2

Eilon — Fri, 20 Nov 2009 00:37:06 GMT

sorin

>>>>>>>> I get this error

>>>>>>>> Converting between two versions of Visual Studio is not supported

Hi sorin,

That error can occur if you try to convert a project that was build with Visual Studio 2010. Right now this tool only supports projects built with Visual Studio 2008.

Thanks,

Eilon

re: Migrating ASP.NET MVC 1.0 applications to ASP.NET MVC 2

Eilon — Fri, 20 Nov 2009 00:36:56 GMT

Donn Felker

>>>>>>>>>> Does this converter rely on project type guids? Reason I ask is because all of my MVC Projects do not contain the MVC project type guid (so users can download them from my blog after a presentation and not have to have MVC installed - I include the binaries in my d/l's).

Hi Donn,

The converter relies on the project type GUID for certain parts of the functionality. Some features require that you use the MVC project type GUID, such as to decide whether to add the updated JavaScript files. Other features check whether the project is any kind of class library in order to update references of System.Web.Mvc.dll from 1.0.0.0 to 2.0.0.0. This is to support the scenario where you have a class library project that contains helpers or controllers that you want to convert.

A workaround is to temporarily add the project type GUID (which should be {603c0e0b-db56-11dc-be95-000d561079b0}), run the converter, and then remove the GUID (which will then be {f85e285d-a4e0-4152-9332-ab1d724d3325}).

Thanks,

Eilon

re: Migrating ASP.NET MVC 1.0 applications to ASP.NET MVC 2

Eilon — Fri, 20 Nov 2009 00:33:56 GMT

Karl

>>>>>>>>>> Any chance on getting source code. This doesn't work as is for me. Its failing when looking for specific javascript files...I'm not crazy enough to use the default MVC structure, or leave in all the gunk js the default project uses.

I am fixing this bug in the tool and will re-release it with support for ASP.NET MVC 2 Beta. I will see if I can get the source code published as well. We do plan to integrate most of this functionality into Visual Studio 2010 as well.

Thanks,

Eilon

re: Sys.WebForms.PageRequestManagerParserErrorException - what it is and how to avoid it

Stan — Thu, 19 Nov 2009 02:50:06 GMT

I have the same issue that "-R" reported in this thread on October 18, 2007. I have a Gridview that allows users to Edit rows. The only time I get the error is when the user enters any kind of HTML tag in a textbox in the row being edited. Like, if the user enters "<b>some text</b>" in a textbox, then the error shows immediately when the user clicks on the Update commandbutton (and I just tested it and it also shows the error if the user clicks on the Cancel command button after entering HTML code in the textbox).

If anyone has any advice for this causing the error, I would really appreciate it.

re: Migrating ASP.NET MVC 1.0 applications to ASP.NET MVC 2

matthewreily — Mon, 16 Nov 2009 17:38:36 GMT

Worked great for me! Thank you

re: Migrating ASP.NET MVC 1.0 applications to ASP.NET MVC 2

irobinson — Sun, 15 Nov 2009 21:57:06 GMT

This worked quite well for me on a project that was started from the CodeBetter Canvas project.

Although, it did fail until I added a "Scripts" folder in the "Web" project - so that it could add all of the JavaScript files to it.

re: Migrating ASP.NET MVC 1.0 applications to ASP.NET MVC 2

Raj — Sat, 14 Nov 2009 14:37:53 GMT

Event after using the tool, I am not able to open the project. Visual Studio says "The project type is not supported by this installation".

re: Migrating ASP.NET MVC 1.0 applications to ASP.NET MVC 2

Hennie Gottenbos — Sat, 14 Nov 2009 13:23:17 GMT

The conversion worked OK and my project is now happily MVC2 however I do get an error about the web.config: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. This web.config worked great for MVC1 so why is this now cropping up? I am using Visual Studio 2008. Thanks for any suggestions you can give me!

re: Introducing SmartyRoute: A smarty-ier way to do routing in ASP.NET applications

Tim Acheson — Fri, 13 Nov 2009 17:20:38 GMT

I like the sound of this. Implimentations a lot like this have been popular for years, typically achieved through ISAPI filters and rewrite rules.

Conditional rules and mappings like this are very convenient for developers. Conditional rules can help increase productivity by making application development faster and applications simpler.

I love the conditional mappings already built-in with ASP.NET MVC, e.g. between Controllers and Views. I make extensive use of it in my own blog. I also like having the ability to override these conditions, e.g. explicitly specifying the View.

re: Introducing SmartyRoute: A smarty-ier way to do routing in ASP.NET applications

Cristian — Thu, 12 Nov 2009 12:20:25 GMT

We are using routing to create more advanced SEO URLs like

/{category} -> category.aspx

/{category}/{product} -> product.aspx

the issue is where we need to treat same url patterns like:

/{category}

/{manufacturer}

/{blog}

/{contact}

all these will be treated by same handler.

I haven't found yet an elegant solution to this (besides an if else structure or case) however the URLs are much more relevant than adding a word in URL just to match a pattern

if you have a good solution to this please let me know cristian.micliuc@heavensolutions.com