RE: ASP.NET v4 was prohibited

[Greg Keogh]

e.g update to 
param name=minRuntimeVersion value=4.0.50401.0 /

Have no fear, I fell for that once before. So I globally searched and
replaced the version numbers in my SL hosting pages. This is easy to forget
if you don't use an auto-generated page when you debug. I use specific home
page files when debugging, so I have to manually update the SL version when
necessary.

Greg

___
ozsilverlight mailing list
ozsilverlight@ozsilverlight.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight

Re: ASP.NET v4 was prohibited

[.net noobie]

Not sure if you have done this, but when you upgrade you may want to check
in the .aspx or .html page where the Silverlight Object is hosted and that
the Minimum Silverlight Version is also updated to the correct version you
are using now, in the upgrade process this will be left as SIlverlight 3.x

e.g update to

param name=minRuntimeVersion value=4.0.50401.0 /

On Thu, Aug 26, 2010 at 12:00 PM, Greg Keogh g...@mira.net wrote:

  D’oh! The answer came just after I posted my puzzle.



 After bumbling around all over the place I found that *Web Service
 Extensions* node in IIS manager had a new entry ... 
 ASP.NEThttp://asp.net/v4.0.30319 which was set to Prohibited by default.



 Tricky eh!



 Cheers,

 Greg

 ___
 ozsilverlight mailing list
 ozsilverlight@ozsilverlight.com
 http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight


___
ozsilverlight mailing list
ozsilverlight@ozsilverlight.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight