OK..

There has been a problem found when using .NET 4.0..

I am downgrade to .NET 3.5 but they are working on figuring out why .NET 4.0 is causing issues with the code and they have reproduced our issue in house.. So its a matter of time until they release a official fix or update us on a work around..

For now. I am downgrading to .NET 3.5

thank you for the infos!
So meanwhile i will install a clean 3.5 version.

Ok.. dont make my mistake..

Dont go download .net 3.5 framework...

its already included.. in windows 7.. to enable it..

http://www.sql-articles.com/articles/troubleshooting/dotnet-35-on-windows-7-to-install-sql-server-2008

Its a windows feature.. and the installer does nothing... but blinks when you click on it.. sometimes...

Hi,

we have found what is causing the issue and we are working on a solution for .Net 4.0. The problem is that some of out assemblies are not loaded when MonoX is switched to the .Net 4.0 due to the issue related to "PrecompiledApp.config" - basically this file should tell the framework to load the App_Browser.dll and other Asp.Net related files but on .Net 4.0 these files are not loaded and you may face an issue that rewriting and page cache not working. In the meanwhile you can:

1. downgrade to 3.5 like you already did
2. you can delete the "PrecompiledApp.config" but we think that you will need to recompile the application using the provided solution under the .Net 4.0 

We will keep you posted.

Regards

To make things clear, removing PrecompiledApp.config under 4.0 may result in other side effects (Global.asax events not being called, resulting in page caching functionality being disabled).
This is an undocumented flaw in 4.0. We are planning to solve it by offering separate installations for different versions of .NET framework. We did try to stick with a "single package fits all" strategy for as long as we could, but such annoying issues force us to change the approach. It will probably make your lives easier too, since everything will work out of the box, without moving config files around.

TO confuse us even more..

Microsoft decided not to list .NET version 3.5 as so.. instead it shows up in IIS 7 as .. 2.0.50727.1434

So if you configure the service to run in the application pool of 2.0.50727..
then you configured it to run under .net 3.5

More information of this can be found here
http://www.west-wind.com/weblog/posts/289139.aspx

Ok.. Now Im finally able to install it by setting up the .net IIS pool to 2.0.50727.. AKA .NET 3.5.

Yes, you need to select the .NET 2.0 which then can be .NET 2.0 or 3.5 but that is defined by the web.config assembly references etc. This is a normal thing because .NET 3.5 wasn't designed as a new CLR just a another layer on top of the existing .NET 2.0 framework.

There was no problem when downgrading anymore!
I'm looking forward to see the new packages :)

Thanks for you fast help, very impressive support!!