Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-winehq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-winehq
Commits
3ece2461
Commit
3ece2461
authored
Jul 09, 2004
by
Mike McCormack
Committed by
Alexandre Julliard
Jul 09, 2004
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Cosmetic fixes.
parent
7231a439
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
10 deletions
+10
-10
action.c
dlls/msi/action.c
+10
-10
No files found.
dlls/msi/action.c
View file @
3ece2461
...
...
@@ -877,7 +877,7 @@ UINT ACTION_PerformAction(MSIHANDLE hPackage, const WCHAR *action)
rc
=
ACTION_PublishProduct
(
hPackage
);
/*
Called during i
t
unes but unimplemented and seem important
Called during i
T
unes but unimplemented and seem important
ResolveSource (sets SourceDir)
RegisterProduct
...
...
@@ -3114,8 +3114,8 @@ static void resolve_keypath(MSIHANDLE hPackage, MSIPACKAGE* package, INT
/*
* Ok further analysis makes me think that this work is
* actually done in the PublishComponents and PublishFeatures
* step
. A
nd not here. It appears like the keypath and all that is
* resolved in this step, however act
au
lly written in the Publish steps.
* step
, a
nd not here. It appears like the keypath and all that is
* resolved in this step, however act
ua
lly written in the Publish steps.
* But we will leave it here for now
*/
static
UINT
ACTION_ProcessComponents
(
MSIHANDLE
hPackage
)
...
...
@@ -3440,12 +3440,12 @@ static UINT register_appid(MSIHANDLE hPackage, LPCWSTR clsid, LPCWSTR app )
static
UINT
ACTION_RegisterClassInfo
(
MSIHANDLE
hPackage
)
{
/*
*
again i
am assuming the words, "Whose key file respesents" when refering
* to a Component as to mean
in that
Components KeyPath file
*
Again I
am assuming the words, "Whose key file respesents" when refering
* to a Component as to mean
the
Components KeyPath file
*
* Also there is a very strong connection between ClassInfo and ProgID
* that
i
am mostly glossing over.
* What would be more proper is to load the ClassInfo and the ProgID info
* that
I
am mostly glossing over.
* What would be more prop
p
er is to load the ClassInfo and the ProgID info
* into memory data structures and then be able to enable and disable them
* based on component.
*/
...
...
@@ -3993,7 +3993,7 @@ static UINT ACTION_CreateShortcuts(MSIHANDLE hPackage)
* 99% of the work done here is only done for
* advertised installs. However this is where the
* Icon table is processed and written out
* so that is waht
i am going to do here
* so that is waht
I am going to do here.
*/
static
UINT
ACTION_PublishProduct
(
MSIHANDLE
hPackage
)
{
...
...
@@ -4082,7 +4082,7 @@ static UINT ACTION_PublishProduct(MSIHANDLE hPackage)
}
/* Msi functions that seem approp
er
ate here */
/* Msi functions that seem approp
ri
ate here */
UINT
WINAPI
MsiDoActionA
(
MSIHANDLE
hInstall
,
LPCSTR
szAction
)
{
LPWSTR
szwAction
;
...
...
@@ -4110,7 +4110,7 @@ UINT WINAPI MsiDoActionA( MSIHANDLE hInstall, LPCSTR szAction )
UINT
WINAPI
MsiDoActionW
(
MSIHANDLE
hInstall
,
LPCWSTR
szAction
)
{
TRACE
(
" exteral attempt at action %s
\n
"
,
debugstr_w
(
szAction
));
TRACE
(
" exter
n
al attempt at action %s
\n
"
,
debugstr_w
(
szAction
));
return
ACTION_PerformAction
(
hInstall
,
szAction
);
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment