PBDev - PureBasic Developer - freeware version

[ts-soft]

Don't know what you mean.
Settings like the environmentsettings?

Yes, better put the ini-file to appdata and add the manifest
for vista user (no virtualisation more)

Greetings
Thomas

[Edwin Knoppert]

I am aware of that 'solution' but frankly, i want to know why it works on my computer first.

BTW, what manifest detail are you referring to?

[ts-soft]

BTW, what manifest detail are you referring to?

You found the manifest in the compileroptions from the PB-IDE. Without the extra settings
for Vista, your application goes in compatible mode with virtualisation (Virtual Store and so on)

But without changing the place of the INI, you should not add this manifest to your application!
Is only for real Vista or 7 compatible programs

[Edwin Knoppert]

I have no idea what you mean.
PBDev has no manifest at all.
It doesn't since the propertybox is not working properly with a manifest.

Exe's created with PBDev will get a manifest (to enable theming) which is maintained via the projectsettings.
I forgot where i get the manifest from though, embedded in PBDev or i use the PureBasic's version, i have to chechk that but then we have a discussion about exe's created??

Make sure you be clear, is it PBDev not using it's INI properly?
Then like i said, why does it work on my computer?
PBDev does not use a manifest itself.

[ts-soft]

Make sure you be clear, is it PBDev not using it's INI properly?
Then like i said, why does it work on my computer?
PBDev does not use a manifest itself.

PBDev using the INI, but not the right way for multiuser noadmin windows systems.
Is not a problem on my home PC but for Business Users is no way to change the environment settings
and all users use the same settings.

Your old way is no recommend by MS but it works

Greetings
Thomas
and sorry for my bad english

[Edwin Knoppert]

Oh ok, if you wish to 'share' PBDev amongst other users like on a network then there are a few reasons not to do so:

1)
The INI get's reset by any user whenever he likes.
If PBDev itself was intended to be a multiuser app it should be using the registry (the app data folder is a solution as well)
(An INI file is easier to transfer if you must, therefore..)

2)
The license does not allow multiple users on a single licensefile.
A license is for a specific user only.
Of course you can circumvent this by purchasing multiple licenses and keep using a single license, no big deal.
But then you'll run into other sharing limits of the program.

3)
The free version, the one without a license may not be used for commercial purposes, this rules out multiuse imo anyway (using it on a network).

4)
How many developers can we expect here..? one, two?
This is not a microsoft office scenario, a simple user install would solve all of these issues.
We have 3 programmers at the office and 3 licenses for visual studio, we install this stuff manually on the local disk.

--

In the mean time i was thinking about your reply, the one before and i was thinking maybe he wants the extra settings the compiler provides for the target exe.
Anyway, it may be wise for me to check this out.

[Edwin Knoppert]

>Is not a problem on my home PC but for Business Users is no way to change the environment settings

I may have misunderstood this line.
Can it be that your office PC (BU) would not allow to let PBDev save these settings?
And does not use a network install?
That may be the problem i was asking for, that means when you are not admin + using PBDev using an INI in the PBDev folder it will not be able to update that?

?

[SFSxOI]

Don't know what you mean.
Settings like the environmentsettings?

The setup requires admin access or at least an extra warning is what you get.

I just used my W7 RC to do this setup and afterwards i set the compiler filename stuff.
I have restarted PBDev and the compiler was still set.

Huhhhh...the RC permissions stuff is a little different then the RTM versions, They changed some stuff from the RC right before retail and RTM. But I got it working now, and yeah admin is needed for full function it seems, at least here. I'd recommend people use the retail (or RTM if they have it) for further testing for anything to do with Windows 7, there are a lot of subtle changes behind the scenes between the RC and the actual RTM. I got my RTM from MS for beta testing so i've had a chance to compare the two, and there are some differences in this area that may affect some things.

[ts-soft]

>Is not a problem on my home PC but for Business Users is no way to change the environment settings

I may have misunderstood this line.

On my business, i'm not an admin or can start the program with admin-privileges, so i can't change any settings,
the still ignored.

[Edwin Knoppert]

I am sorry about that, please ask permission.
Maybe i'll consider a rewrite to use the appdata instead... ever..
Anyway, this may be a different issue isn't?
I mean, i don't think some manifest will help you to let an app write its ini in the pf folder.
This is a sysop setting towards users.
He may be that friendly to adapt your PBDev folder for this.

--

The setup has an overlay icon (some shield logo) to indicate it requires admin settings.
I read somewhere it is a common setting for inno setup.

[Edwin Knoppert]

Ok, i have modified the exe to allow the INI from the AppData folder.

It is using it like: CSIDL_APPDATA + "PBDEV\PBDEV.INI"
If it finds the INI in there it will use that one.
Otherwise it uses the one near the exe.

If you are not sure what folder to choose start cmd.exe and type SET (+ enter)
Scroll back to APPDATA and it shows it self like: APPDATA=C:\Documents and Settings\Edwin Knoppert\Application Data

Navigate to that (hidden!) folder and add folder PBDev and place the PBDev.INI in that folder.
This could be an empty file created with notepad..

Hope this is sufficient.

[ts-soft]

Thanks for this changing

[Edwin Knoppert]

I did a brief test today with 4.50.
PBDev seems to work fine.

[blueb]

Thanks Edwin,

I know not many are using your fine product... but I am!

--Bob

[Edwin Knoppert]

One of the last!

haha