Author Topic: Published solution errors when opening mainform  (Read 3015 times)

larryhts

  • Jr. Member
  • **
  • Posts: 98
    • View Profile
Re: Published solution errors when opening mainform
« Reply #15 on: June 01, 2018, 03:30:22 PM »
Thanks Archie, I'll post if I get them back. Thanks for your time.

bachphi

  • Hero Member
  • *****
  • Posts: 653
    • View Profile
Re: Published solution errors when opening mainform
« Reply #16 on: June 01, 2018, 05:19:12 PM »
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.

===================================================
This is NOT alt.read.my.mind.
No such thing is sh^t-for-brains unless you are posting to alt.read.my.mind.
===================================================

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5317
    • View Profile
    • AdvancedHMI
Re: Published solution errors when opening mainform
« Reply #17 on: June 01, 2018, 05:36:51 PM »
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.

bachphi

  • Hero Member
  • *****
  • Posts: 653
    • View Profile
Re: Published solution errors when opening mainform
« Reply #18 on: June 01, 2018, 06:02:22 PM »
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.
« Last Edit: June 01, 2018, 06:16:11 PM by bachphi »
===================================================
This is NOT alt.read.my.mind.
No such thing is sh^t-for-brains unless you are posting to alt.read.my.mind.
===================================================

bachphi

  • Hero Member
  • *****
  • Posts: 653
    • View Profile
Re: Published solution errors when opening mainform
« Reply #19 on: June 01, 2018, 06:20:29 PM »
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 NOT alt.read.my.mind.
No such thing is sh^t-for-brains unless you are posting to alt.read.my.mind.
===================================================

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5317
    • View Profile
    • AdvancedHMI
Re: Published solution errors when opening mainform
« Reply #20 on: June 01, 2018, 06:36:48 PM »
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.