Got an idea for enhancing PureBasic? New command(s) you'd like to see?
-
mback2k
- Enthusiast

- Posts: 257
- Joined: Sun Dec 02, 2007 12:11 pm
- Location: Germany
Post
by mback2k »
It would be cool if PBCompiler would put the information that is entered in the compiler options into the Manifest file.
The following should be replaced:
- version="1.0.0.0"
- name="CompanyName.ProductName.YourApp"
- <description>Your application description here.</description>
Code: Select all
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="CompanyName.ProductName.YourApp"
type="win32" />
<description>Your application description here.</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*" />
</dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="asInvoker"
uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
-
c4s
- Addict

- Posts: 1981
- Joined: Thu Nov 01, 2007 5:37 pm
- Location: Germany
Post
by c4s »
is it good to fill these fields (version, name, description) manually or does the pbcompiler ignore it for a reason? Could I do something wrong?
If any of you native English speakers have any suggestions for the above text, please let me know (via PM). Thanks!
-
jassing
- Addict

- Posts: 1885
- Joined: Wed Feb 17, 2010 12:00 am
Post
by jassing »
{{bump}}
it's getting old manually hacking the manifest. would almost prefer that no manifest was automatically added..
Really should have this built in for the windows compiler, adjust version, elevation level, version etc.
-
MachineCode
- Addict

- Posts: 1482
- Joined: Tue Feb 22, 2011 1:16 pm
Post
by MachineCode »
jassing wrote:it's getting old manually hacking the manifest. would almost prefer that no manifest was automatically added.
Disabling XP skins in the Compiler Options will not add it.
Microsoft Visual Basic only lasted 7 short years: 1991 to 1998.
PureBasic: Born in 1998 and still going strong to this very day!
-
jassing
- Addict

- Posts: 1885
- Joined: Wed Feb 17, 2010 12:00 am
Post
by jassing »
MachineCode wrote:jassing wrote:it's getting old manually hacking the manifest. would almost prefer that no manifest was automatically added.
Disabling XP skins in the Compiler Options will not add it.
well, I never used xp skins, so 'disabling' it isn't an issue... Why doesn't the compiler grab the relevant information from the version/resources?