innie

Hi, I understand the benefits of .NET 3.5, however on our network environment there is no roadmap to update from .NET2.0 due to many many applications which will need testing on .NET3.5 So, PDN3.36 suits my situation. The Functionality that PDN3.36 provides is more than enough for our end users. I will stress that there is no upgrade path forward from 3.36 unless the .NET Framework is pushed to 3.5. Many thanks to the great work being done here.

Oh Dear, you can flame me for my first post!. I refered to PDN3.6, but Pyro clarified in his post 3.36. I checked and yes I am running 3.36. Please accept my apologies.

Thankyou pyrochild for that clarification. What you are saying is supported by what i am seeing on my desktop. PDN3.36 is working fine on .net 2.0. My understanding too was that a lot of the new framework is around the installer and application management. I would still like to know if PDN3.5 has application enhancements dependent on .net3.5?

Then howcome i am running paint.net 3.36 on a machine with the .net 2.0 framework? It certainly isn't "inoperable"

hello, This is a first post for me. I was wondering what features of Paint.net are actually rendered inoperable if installing on a Framework 2.0 Machine? In our environment, our PC's run XP SP2 with .net 2.0 framework and there is no current roadmap to go to .net3.5. I have trialled Paint.net 3.6 on 2 machines runing .net2.0 and so far i haven't had any problems? Is it too much of a risk to install paint.net 3.6 on a .net 2.0. framework?