AdvancedHMI Software
General Category => Support Questions => Topic started by: larryhts on June 01, 2018, 09:44:32 AM
-
I have a published solution that I was going to edit to add one more data point and when I open it in VB it opens fine but when I try to open the main form designer it gives me 66 errors. Its been running for over a month. Nothing changed on the files????????? Not sure what to do at this point.?
-
Can you give an example of some of the errors?
-
Do you happen to upgrade or use a different version of visual studio?
-
Screen shots of errors trying to open MainForm No changes or updates???
-
Can you post a screen shot of what you see in Solution Explorer? Did you try to Clean Solution and Rebuild?
-
Archie, I did do the clean and rebuild. By that I mean I deleted the bin and obj files.
-
My first suspicion was the AdvancedHMIControls project was not being recognized, but that does not seem to be the case.
My next suspicion is that something happened to the references. Expand down the references in the AdvancedHMI and AdvancedHMIControls project.
-
Did you by any chance use the Publish function with this project? If so, then we need to try to back out some things. Start with deleting the temporary key file.
-
yes I did use the publish in VB?????? How should I publish?
-
sorry about that
-
This is the recommended method of deployment:
https://www.advancedhmi.com/forum/index.php?topic=14.msg37#msg37
I classify the Publish tool as "evil" because you will most certainly discover one of its quirks the hard way. In your case I believe this is the expiration of your temporary key. Deleting the key may resolve it. If not you will need to generate another key that will give you another year.
-
Archie, What is the "temporary key" and where would I find It.
-
Archie, What is the "temporary key" and where would I find It.
In Solution Explorer under the AdvancedHMI project.
-
Archie, How should I go about fixing this app as we are the end user. I have 2 of these that I used the publish on. I will be using the other way from now on.
-
In all honesty, I really don't know how to completely undo all of the changes that Publish does to a project. Many years ago after falling into the quirks of Publish, I never used it again.
If you right click the AdvancedHMI project and go to Properties, the security tab and Publish tab may have some settings like "Enable Click Once Security" that needs to be unchecked.
-
Thanks Archie, I'll post if I get them back. Thanks for your time.
-
Not to mention that it's not compliance to your GPL licensing requirement:
https://www.advancedhmi.com/forum/index.php?topic=1092.msg11623#msg11623
Archie, why not have a "publish" button of your own: something like spawn a process, close out application,
zip the \bin\Debug folder to TargetFolder, next zip up entire source and put it under TargetFolder\Source.
-
Archie, why not have a "publish" button of your own: something like spawn a process, close out application,
zip the \bin\Debug folder to TargetFolder, next zip up entire source and put it under TargetFolder\Source.
The only way that I would really know how to do this would be with an VS extension. That would require installing an additional item after installing VS.
-
OK, it's not that easy then, lol.
So everyone please, here is the proper way to PUBLISH your project and comply with the great licensing requirement:
1. Copy .\AdvancedHMI\bin\Debug folder to Target folder.
2. Close out you application & Zip up the entire folder to TargetFolder\Source.
3. If the PC is on factory floor and for certain reason, that you dont want put the source.zip there, then put a copy of Readme.txt and UsageAndLicense.txt. A ReadMe.txt stating that this project use open source and EndUSer have the right to ask for a complete project source.
-
Another idea that come to my mind, is why not just include the UsageAndLicense.txt file in the debug folder. I would also add a statement about the end user have the right to ask for complete source.
-
Another idea that come to my mind, is why not just include the UsageAndLicense.txt file in the debug folder. I would also add a statement about the end user have the right to ask for complete source.
This is a good idea that I will implement in the next release.