I’ve done a simple test with LINQ to SQL on Win24, but as I expected LINQ demands more reflection permissions than currently granted under medium trust. A solution can be found here (second part of the article).
I would like to ask if JodoHost will consider making this change, because without it the use of .NET 3.5 will be severely crippled.
NOTE: Making this change will also grant this policy to ASP.NET 2.0 websites running on the same server. We have determined this to be an acceptable change for hosted sites that run under medium trust. This change will have no impact on existing ASP.NET 2.0 websites that can run under medium or partial trust.
Before .NET 3.5 was even released, I’ve seen some posts on the internet from people that consider granting this permission ‘scary’ in a shared hosting environment. However, I’ve yet to see any solid arguments for their case.
I planned to do this over the weekend but had a major disaster happen and did not even sleep over the weekend due to this.
I can’t get into details it wasn’t family or health or anything, just loads of wasted time and lessons learned(not related to any client here or anything)
I will be on this tonight on win27 and win3 and then expand it tomorrow.
Looking forward to giving it another try..
I had some misunderstanding between myself and LINQ to SQL last night during a migration in a production environment.. still a bit rusty on how some of it works and I could use the practise :rolleyes:
I’ve only done a very basic test so far, but it works like a charm
Now to find some hobby project to mess around with it.. and the time to do it.
(Win24)
What about win21 ? - I have a client that needs it, I can move the site to win27 but they are afraid they will loose search engine rankings if change the server.
