Messages
Reply to this message07:17 pm
3N715D1WV
| From: | JeffL |
| To: | Rick Strahl |
Everything is now working.
Thanks, Rick!
Hi Jeff,
Ok I think I know what's happening...
Can you do the following:
- Uninstall Help Builder from Programs and Features
- Delete folder <program files>\West Wind Html Help Builder
- Then reinstall from the same file you downloaded previously
The issue is that there's an old copy of the wwReflection (and possibly other) assemblies sitting in the root from the previous version. This is causing the wrong assembly to be loaded during hte import which in turn is missing some of the new features.
Another way to do this (if you don't want to reinstall): Delete all the DLLs in the install folders root path - all the DLLs have been moved into the /bin folder in the latest releases.
Sorry for the hassle - I expected that the automatic uninstall would have removed those files but apparently that's not happening.
+++ Rick ---
Yes, the download worked and I'm now running build 4.675.
Got the same OLE error Importing the Assembly, but the reporting of the error to you worked and you should have the error and my steps now.
I tried it with both .NET options. Using the .NET Type it does present a treeview with all the .NET properties and all with checkboxes to select or not select.
Hi Jeff,
Had a chance to double check the version. Looks like the FTP upload last night didn't make it to the server - the file was old. Sorry, but can you try doing another install from the same location the new file is definitely up there now.
+++ Rick ---
Rick,
I went to the link below and installed from there, but I'm getting the same errors and the other errors when I submit the bug to you.
Jeff,
Can you go ahead and reinstall Help Builder from:
http://west-wind.com/wwHelp/download.aspx
This install should install right ontop of your old installation and I've posted this now as an unofficial release (that doesn't auto-update at this point yet) since there are a few small tweaks and fixes.
Retry your import and see what happens now.
I fixed the error reporting bug (which I'm not sure how that didn't work since the include file was there?) and there are also a host of improvements to the external preview to avoid Windows 7/8 security issues. If you still see a failure you should now get the error dialog and the bug reporting window which hopefully will give us a little more information on what's failing in your import. It's also possible that this was fixed since I've made a few small tweaks to the Reflection engine. As I said it works for me here...
+++ Rick ---
So I tried your DLL and it works for me...
I'm going to send you an updated build just to make sure we're on the same page here.
+++ Rick ---
Doh!
Sorry about that. We recently changed our email policy where ALL email goes out encrypted or ends up in that verification signup crap unless I add [u] to the subject line.
I've sent you the DLL again.
Hi Jeff,
I didn't get a DLL from you...
I didn't reply to your email because of the Email verification stuff on your inbox - I wasn't about to go through the verification signup... Word of advice: If you want people to respond to your email, lose that feature because it's a pain in the ass. I refuse to reply to emails from anybody that has anything but the simplest click through email verification in place.
Feel free to give me a call and we can take a look at what's wrong (http://west-wind.com/contact.aspx). I can send you an updated build too to make sure we're looking at the same thing.
+++ Rick ---
Rick,
Did you get time to look at my DLL yet?
Thanks
Hi Jeff,
I have some time finally to look closer at this.
Can you do me a favor and give me exact steps and possibly email me a copy of the DLL you're importing?
Specifically - are you importing the entire .NET assembly or are you importing one class (or many classes) explicitly with "Import .NET Type"?
I'll check it out here nad if that does work I can send you a slightly later build of Help Builder that might have this addressed (although I'm not sure what would be different since I don't think this code has been updated). The other thing that will be useful about this is that I can debug code on so we potentially get a little more information out of the error message that might give a better clue as to what's failing.
Thanks and sorry for the delay,
Aloha,
+++ Rick ---
Rick,
I ran as Admin and it had the same OLE error.
Hi Jeff,
Hmmm... odd, I don't see this here...
Can you do me a favor and try with "Run As Administrator"? I wonder if there's some sort of security issue getting in the way there...
I can take a closer look at this on Friday - unfortunately I'm out travelling at DevConnections these next days, so not much time to investigate further until then...
+++ Rick ---
I pick Import from the Tools menu and I import a .NET Assembly. I pick my DLL. I take the defaults and hit finish.
I get the error message OLE. And then on self-report I get another FoxPro error and then it shuts down.
Interestingly, when I re-open HTML Help Builder and open my project I do see that it managed to bring in one Namespace and the beginning of it's first class, but not much is filled out.
Hmmm... that's odd. Can you give me exact steps?
+++ Rick ---
I was upgrading from version 4.0 Build 4.601.
Ok, I used your link to download the installer and I ran that and it worked.
Now, I've got an error trying to bring in a .NET DLL.
The app won't self-report the error because it gets an error saying: "Variable 'WWHELP_VERSION' is not found.
The original error when it tries to read in the assembly is:
OLE error code 0x80020006: Unknown name.
System Error #1426
Jeff,
What version are you updating from?
4.6 and later requires a full reinstall (which is basically what update does these days anyway).
http://west-wind.com/wwhelp/download.aspx
The install just replaces your existing version...
Aloha,
+++ Rick ---
Rick,
I'm running HTML Help Builder version 4.0 Build 4.601 and when I try to upgrade to latest and greatest it fails with a 'syntax error'.
Thanks