I am actually the developer of Managed Fusion Url Rewriter. The Url Rewriter doesn't need to be compiled to 4.0 to work under 4.0. You can leave it compiling under 2.0 and it will still work with the integrated pipeline on IIS and .
NET 4.0. You can download the latest source from here: github.com/managedfusion/managedfusion-r... Also I created a project that allows you to define your MVC routes in your rewriter config log here: github.com/managedfusion/managedfusion-r... And can read more about the project here: coderjournal.com/2010/03/editable-mvc-ro... As for the 500 errors, I am probably going to need a little more information, can you please update your post to include maybe a log from the rewriter enabled by adding the following to the top of your rewriter: RewriteLog "log. Txt" RewriteLogLevel 9 This should help us better diagnose where the 500 error is coming from.
But given all of have written above, I have concerns that you may not understand the difference between routes and rewriting, which many developers don't because they are sort of similar in what they accomplish. Which is why I wrote the following post: http://coderjournal.com/2010/03/difference-between-routing-rewriting If you want to work off line from StackOverflow back on the forum I would be happy to help you http://urlrewriter.codeplex.com/Thread/View.aspx?ThreadId=228348.
I am actually the developer of Managed Fusion Url Rewriter. The Url Rewriter doesn't need to be compiled to 4.0 to work under 4.0. You can leave it compiling under 2.0 and it will still work with the integrated pipeline on IIS and .
NET 4.0. You can download the latest source from here: github.com/managedfusion/managedfusion-r... Also I created a project that allows you to define your MVC routes in your rewriter config log here: github.com/managedfusion/managedfusion-r... And can read more about the project here: coderjournal.com/2010/03/editable-mvc-ro... As for the 500 errors, I am probably going to need a little more information, can you please update your post to include maybe a log from the rewriter enabled by adding the following to the top of your rewriter: RewriteLog "log. Txt" RewriteLogLevel 9 This should help us better diagnose where the 500 error is coming from.
But given all of have written above, I have concerns that you may not understand the difference between routes and rewriting, which many developers don't because they are sort of similar in what they accomplish. Which is why I wrote the following post: http://coderjournal.com/2010/03/difference-between-routing-rewriting/ If you want to work off line from StackOverflow back on the forum I would be happy to help you. http://urlrewriter.codeplex.com/Thread/View.aspx?ThreadId=228348.
I'm trying to take a .net 2.0 app into the .net 4.0 world. We are leaving the webforms as is and adding new functionality in MVC2. While we could redo all of our managed fusion rewrites as mvc routes, so for the moment, I'd rather just add the new routes to MF and have it handle url rewriting duties for both webforms and controllers.
I got it working on .net 3.5, but when the web app is compiled to 4.0 and the app pool set to 4.0, any url throws a 500 error. Nothing interesting appears in the event logs either. I tried downloading the source and compiling MF to 4.0, but no dice.
Any suggestions on getting this to work? Is there a way to get MF to output detailed errors that can help identify the problem?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.