 |
|||||
|
As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Join the TIBCO Community
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community. | |||||
Read-Only TopicGo | Search | Notify | Tools |
| Maintain Deployment Issue | Login/Join |
| Master |
All When creating a Maintain application with forms, XML code gets added to the bottom of the MNT file. When you open the file inside the Maintain Development Environment (MDE), the XML is used to rebuild and display the forms. When an MNT file gets deployed to a server, a Winforms file is created, and the XML is stripped out of the file. I believe this was done to reduce the size of the MNT file on the server. The issue is a file deployed to the server cannot be reopened in the MDE. Of course, as seasoned programmers, we ALL back-up our code, but there are unforeseen issues. Sometimes the source files just disappear and you would have to recreate your forms from scratch. I am proposing that we change the deploy option to always deploy the XML with the MNT file. There will be an option in the deploy scenario to turn this off. This way, deployed forms can still be edited. Is there anyone in this community that feels this is a bad idea? Please let me know. Thanks Mark Derwin | ||
|
| Virtuoso |
Mark, Your proposal is to have the xml included in the deployed mnt file, as well as have a wmf file created? Or is it to get rid of the wmf file creation? Anyway, both options would have my support. I've had it happen more than once that because of intermittent network problems the development files got corrupted. If I had the option to copy back from the just deployed files, it would have saved me loads of time. Another option to possibly circumvent this is to have the CDE create backups of the development files, so that there would always be at least the copy of the previously saved maintain. GamP
| |||||||||
| ||||||||||
| Master |
We would still create the Winforms files. The Winforms are used at runtime. The XML is just for development. As for the BAK files, we got rid of those a while ago. Must have been for space. Can't imagine why anyone would not want a backup. Mark | |||
|
| Platinum Member |
Mark, excellent suggestion. Kudos. I too have had those 'unfortunate scenarios' where suddenly it was gone... (thank goodness for backups). Ira. 5.3.6 aix aix-533,websphere 5.1.1,apache-2.0, wf 538(d), 537 (p), ============== 7.6.11 (t) aix 5312 websphere 6.1.19 apache 2.0 | |||
|
| Platinum Member |
I strongly agree that this issue needs some attention. I lost a day or two trying to work on a set of deployed files, before learning this hard lesson. In my darker moments I wished I could bill that time to IBI  As to how to handle the files, consistency is very important (in the programmers UI) and that is what is broken when the deployed.mnt file is different then the development .mnt. So I think that having them retain the same characteristics on all platforms is the way to go.This message has been edited. Last edited by: Dave Ayers, | |||
|
| Powered by Social Strata |
 | Please Wait. Your request is being processed... |
Read-Only TopicCopyright © 1996-2020 Information Builders
| View $GS_USERNAME's Public Profile |
| Add $GS_USERNAME to my Ignore List |
| View Recent Posts by $GS_USERNAME |
| Notify me of New Posts by $GS_USERNAME |