3.5 compatability

  • Thread starter Thread starter UpRider
  • Start date Start date
U

UpRider

My web host provider uses Windows Server 2003, IIS6, .Net Framework 2.0 and
SQL Server 2005. They have no firm plans to upgrade to .Net 3.5.
I create my website (www.dbtc.org) with (mostly) Expression Web and (some)
Visual Web Designer 2005 Express.
I'm kinda geeky and like to use the latest stuff, and want to use VWD 2008
Express. Can I? Is there any way to have VWD 2008 not use the enhanced .net
3.5 features so that the host provider sees only .Net 2.0?
If I do use advanced features and compile it locally before uploading, will
that work?
If my host provider stalls, is .Net 3.5 with VWD 2008 so overwhelmingly
better that I should change to a new host provider?

TIA and raring to go,
UpRider
 
Hello UpRider,

u can try to upload your .net 3.5 assemblies into bin folder of website and
reference them from there (but u need to set the trust="Full" in web.config,
if only your hoster supports this)

it could help for some assemblies because they may be compatible with .NET
2.0

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo


U> My web host provider uses Windows Server 2003, IIS6, .Net Framework
U> 2.0 and
U> SQL Server 2005. They have no firm plans to upgrade to .Net 3.5.
U> I create my website (www.dbtc.org) with (mostly) Expression Web and
U> (some)
U> Visual Web Designer 2005 Express.
U> I'm kinda geeky and like to use the latest stuff, and want to use VWD
U> 2008
U> Express. Can I? Is there any way to have VWD 2008 not use the
U> enhanced .net
U> 3.5 features so that the host provider sees only .Net 2.0?
U> If I do use advanced features and compile it locally before
U> uploading, will
U> that work?
U> If my host provider stalls, is .Net 3.5 with VWD 2008 so
U> overwhelmingly
U> better that I should change to a new host provider?
U> TIA and raring to go,
U> UpRider
 
You can go back and force between 3.5 and 2.0 as long as you are not using
features from 3.5
I have a project where i develop in VWD 2008 but upload (just copy all .cs
and .aspx files) to 2.0 enviroment.




George.
 
vs2008 supports creating/editing 2.0 websites. under the build, pick 2.0 as
the target.

note: 3.5 support is implemented via web.config, with overrides for dll
versions, and references added to the new 3.5 dlls. you can open web.config,
strip these out, and you have a 2.0 site.


-- bruce (sqlwork.com)
 
New multi-targeting support allows you to create ASP.NET 2.0 or 3.5
applications.
So yes you can create an ASP.NET 2.0 application, but you won't be able to
use most of the cool new features Microsoft as implemented since then.

--
I hope this helps,
Steve C. Orr,
MCSD, MVP, CSM, ASPInsider
http://SteveOrr.net
http://iPhonePlaza.net
 
Thanks to Michael, George, Bruce and Steve. I appreciate your sharing your
expertise.

UpRider
 
Back
Top