Hi,

(I hope this is the appropriate forum for my enquiry - I thought 3.5 users may have experience of this kind of thing)

I am currently developing custom modules on .NET 2.0 and DNN 4.6.2 using Visual Studio 2005. I have identified a third party module, which while unrelated to my module is required in my overall site and it requires version .NET 3.5.

Could someone tell me if the following is feasible/possible?

I install version .NET 3.5 on my development box but continue to develop in Visual Studio 2005 against .NET 2.0. I then target ASP.NET 3.5 in IIS to test whether my custom modules continue to function. If everything is ok I can then purchase and avail of the third party module.

Are there any other changes required to DNN 4.6.2 before it will run under 3.5 (e.g. do I need to recompile it or change any web.config settings or is simply targeting a different version in IIS sufficient). I hope to upgrade soon to a more recent version of DNN (e.g. 4.8 or 4.9) but I'm in the middle of developing my custom module and would like to avoid upgrading to VS2008 in the short term.

Thanks,

Norman