G'day All,

I am experiencing a strange issue when installing Notepad++ using WPI. A feature of the Notepad++ install is the shell extention (right-click) to open files in Notepad++ which is done by registering a dll file either using the NSIS packager or manually.

I have attempted to do this using a silent install and from a command line and neither work (only the dll registration fails) when executed from WPI.

When the program is installed the exact same way but called from a batch file instead of WPI, the shell extension works.

Any ideas why this is happening ?

Hmm..

I think I could have spoken too soon. It appears the dll doesn't want to register at all now.

It was working and has since stopped.

I'll keep investigating

Are you trying on the same machine you registered it first?

Maybe it's already registered on that machine.

Try

regsvr32 /u yourfile.dll

before registering it.

OK, so I rebuilt my VM machine again and ran WPI thru GUIRunOnce and again the DLL did not register.

I call the following batch file from WPI in order to install Notepad++

xcopy c:\build\notepad++\. "%ProgramFiles%\Notepad++\" /e/q/c/y
cscript c:\build\scripts\notepad++.vbs //B
regsvr32 /s "%ProgramFiles%\Notepad++\nppshellext.dll"

Everything works except the DLL registration.

I unregistered the DLL and removed the files then ran the batch file manually and it works fine !?!

This has only started happening since I started WPI. I can't for the life of me see why WPI would be the issue but it worked when I called it from another batch file when using GUIRunOnce.

Any ideas ?

So in another attempt I ran the regsvr32 command in the 'Execute After' in the Options>Tools of WPI.

Wouldn't you know it, it works. So can anyone tell me why it doesn't work during the normal processing of WPI ?

One thing I forgot to ask: are putting those commands directly into WPI or are you creating batch file that contains those?

One thing I forgot to ask: are putting those commands directly into WPI or are you creating batch file that contains those?

his using a batch file .. thats what he said in his previous post

@sadicq I actually tried both ways and neither worked. The only way I have successfully got it to work is by running the regsvr32 line of code in the 'Execute After' section of WPI.

I was messing around rearranging my install order and it now appears to be working again. Not exactly sure how I fixed it though.