innie Posted September 15, 2009 Posted September 15, 2009 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? Quote
david.atwell Posted September 15, 2009 Posted September 15, 2009 The program itself is rendered inoperable. Quote The Doctor: There was a goblin, or a trickster, or a warrior... A nameless, terrible thing, soaked in the blood of a billion galaxies. The most feared being in all the cosmos. And nothing could stop it, or hold it, or reason with it. One day it would just drop out of the sky and tear down your world.Amy: But how did it end up in there?The Doctor: You know fairy tales. A good wizard tricked it.River Song: I hate good wizards in fairy tales; they always turn out to be him.
innie Posted September 18, 2009 Author Posted September 18, 2009 Then howcome i am running paint.net 3.36 on a machine with the .net 2.0 framework? It certainly isn't "inoperable" Quote
david.atwell Posted September 18, 2009 Posted September 18, 2009 I don't even know how that's possible. It might be a fluke, or the fact that Rick hasn't included anything that will finally break on .NET 2.0. Look, the program isn't built for the 2.0 version. Rick can't guarantee it'll even work used this way, and as new releases come out, you never know when it will break. Why not just push your IT department to upgrade? Quote The Doctor: There was a goblin, or a trickster, or a warrior... A nameless, terrible thing, soaked in the blood of a billion galaxies. The most feared being in all the cosmos. And nothing could stop it, or hold it, or reason with it. One day it would just drop out of the sky and tear down your world.Amy: But how did it end up in there?The Doctor: You know fairy tales. A good wizard tricked it.River Song: I hate good wizards in fairy tales; they always turn out to be him.
pyrochild Posted September 18, 2009 Posted September 18, 2009 3.36 is designed for .NET 2.0, but starts to implement things in the installer and updater to get ready for 3.5's requirement of .NET 3.5. Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it!
innie Posted September 20, 2009 Author Posted September 20, 2009 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? Quote
innie Posted September 20, 2009 Author Posted September 20, 2009 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. Quote
pyrochild Posted September 21, 2009 Posted September 21, 2009 Paint.NET 3.5 won't run without .NET 3.5. Sorry. Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it!
Rick Brewster Posted September 21, 2009 Posted September 21, 2009 Paint.NET v3.36 requires .NET 2.0. The website says .NET 3.5 SP1 just to steer people towards the newer .NET version, which will make things easier once the new Paint.NET version comes out, which is ... ... Paint.NET v3.5, and it requires .NET 3.5 SP1. There is absolutely no reason to install .NET 2.0. You should install .NET 3.5 SP1, it is a whole lot better in every imaginable way. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html
innie Posted September 22, 2009 Author Posted September 22, 2009 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. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.