-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error "Object reference not set to an instance of an object" then crash if Office file is opened #7
Comments
By the way, I tried to contact you directly without success: I had trouble to compile the project using VS2015 Community, and if you're interested with french translation, then I might be able to help. |
I'll look into this this evening, but it may work out that the best I can do is give you a more descriptive error message. Also, to open the solution, you will need Visual Studio 2017, although I can roll back to a Visual Studio 2015–compatible project if needed for your translation. Thanks! |
This is fixed in release 1.1.5. Also, where did you get a link to contact me directly, so I can correct that info? |
Well, that's the point, I didn't find any link to contact you directly ^^ |
Ah okay, I'll add a note to the main page that the best method of contacting me is to open an issue. I've also opened issue #8 as a place to coördinate translations, and wrote some basic steps there on how to translate the project's |
Hello,
I was testing your software this evening, and found a bug (using version 1.1.4). Here is the scenario:
I created a XLSM file containing a Module, a class and a UserForm (with a button). On scenario start, the XLSM file is opened.
If you're unable to reproduce the problem, I'll be able to provide my sample XLSM file.
The text was updated successfully, but these errors were encountered: