.net is fantastic... anyone who hates it, doesnt understand it
(yea the framework is big...but HD space isnt an issue in 2010)
(course .net 4.0 is a major cleanup, not to mention the powerfull features it adds)
not to mention its cross platform
its like java,that way
You don't get it.
I have it working now.
My point was, that I was testing an install on a clean system, hopefully like a new user would.
And as it stands it is not seemless with the installers and program you have supplied.
I have now created the following images
base XP plus RideRunner
base XP plus RideRunner in profile mode.
this is so I can check any new plugin installers work and the plugins work with a base RR install.
For my personal install I probably won't go profile mode so I don't care about the
legacy to profile bit.
But anyone starting from scratch will probably come across the same issue and it just paints a poor picture when you get these issues.
base XP (which should NEVER be used)... VISIT WINDOWS UPDATES
get all the required updated (sp3)
the rr installer is OLD OLD OLD OLD, it only LINKS you to framework 2.0 download (NOT sp2)
after installing it... if you had windows UPDATES enabled, it would have prompted you to get your .net updated....
BASE XP(sp3) with .net2.0sp2 or .net3.5sp1(specially if u use CF and u do)
that is where you should start
i updated installer to LINK to
had to pull that link from page source, hopefully MS dont mind the direct link
When I say base xp I mean SP3.
I know there is a reg setting for profile mode, but can we also have a key with the skinpath or at least the folder the files have been moved to.
Just so installers for plugins (and skins) can put the files in the right place.
i thought i showed you the code for your installers , to install in profile mode if found , or is that not what your meaning
I would partialy agree with E... did I just type that????? World must be starting to freeze over....LOL
In dfx5's skin plugin, we did exact that, in its startup, it updates a reg key so that when we release skin update patches it will already know where to look, b/c we know how users like to just copy files from one comp to another so this is a 100% fail safe way.
Originally Posted by carputer1
If I was using the installer program you are using maybe that I would use that code, but I am using NSIS.
However it did point me in the right direction once I had done a legacy to profile conversion.
And it showed me that I can only find out that we are running in profile mode, great, but it doesn't tell me where the files have been moved to.