Re: Vista and the tested but not shipped dll's and ocx files
- From: mindserve <mindserve@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Jan 2008 08:25:01 -0800
That sure is stupid, it seems that Microsoft is making it harder for the user
instead of easier. Most people who I speak to don't even know what the UAC
is. All they know is that they keep getting this annoying pop up box and then
they ask me if my program will run on Apple....
"Galen Somerville" wrote:
In Vista, just because you are the Administrator doesn't really mean much..
You still have to right click and "Run as administrator". Stupid huh!
Galen
"mindserve" <mindserve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:95D08278-72F9-429A-AB72-92F84D879CDE@xxxxxxxxxxxxxxxx
Hi Galen,
These are dll's and ocx files that are normally found in the system32
folder, like msbind.dll Can these go into a data folder as a subfolder? I
wonder if I did this, would it allow it to self register. That would solve
all my problems.
I will try it out and see if this works.
Just a quick question, aren't the default settings for Vista set to
administrator when a user first purchases their new PC with the Vista OS?
Since they have to have at least one administrator, it would seem to be
so.
"Galen Somerville" wrote:
"mindserve" <mindserve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:029FD168-B469-40F2-A515-0D536FD7C5FB@xxxxxxxxxxxxxxxx
Microsoft has tested but did not ship on Vista many dll's and ocx files
that
were shipped with XP. This has caused a problem with my applications. I
have
included them in the setup of the program and they are set to self
register.
I use the visual studio installer and no third party components at all.
I
have about 20 of the dll's and ocx files that install on Vista. Problem
is
that they do not register at all.
I had to create a separate bat file to unregister and then re-register
these
files.
I really need some advice to get the program to install with the UAC on
as
a
normal user would have it and not to have to re-register these files. I
heard
about a manifest but would that be the answer here?
Could I install these files to a different folder on Vista which would
allow
them to register properly?
Assuming the install program is "Project1", this is the manifest file
(Project1.exe.manifest) that I use
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0"
processorArchitecture="X86"
name="Project1"
type="win32"/>
<description>elevate execution level</description>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="requireAdministrator"
uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
If the dll's and ocx's are only used by my programs, I put them in a
"Data"
folder associated wuth my programs.
Galen
- References:
- Re: Vista and the tested but not shipped dll's and ocx files
- From: Galen Somerville
- Re: Vista and the tested but not shipped dll's and ocx files
- From: mindserve
- Re: Vista and the tested but not shipped dll's and ocx files
- From: Galen Somerville
- Re: Vista and the tested but not shipped dll's and ocx files
- Prev by Date: Re: Users can copy text shown on the popup/dialog
- Next by Date: Re: error wile passing custom type variable
- Previous by thread: Re: Vista and the tested but not shipped dll's and ocx files
- Next by thread: Re: Vista and the tested but not shipped dll's and ocx files
- Index(es):
Relevant Pages
|
