Thank you for reporting this bug. We will make it our priority to review this report.
ExtDesigner - Build 1.2.2 Build 48 - Corrupted my .xds file so I cannot open it.
I have a project and added a tree store to it. I was configuring and then did an "export" to test my additions.
The ExtDesigner threw an error: "An unexpected error occurred" - "SyntaxError: Parse error" and gave me the choice to Restart or Exit Designer.
When I restart, it shows the same error and so I am basically stuck. I cannot open by design file to file the syntax error.
I do not want to upload the .xds but can email it Sencha to help investigate the problem
Yikes. Let's get to the bottom of this.
email designer.feedback -at- sencha.com
Top this one...
Just now, I was saving my project when Ext Designer decided to crash... but it didn't corrupt the XDS, no... instead, I now have a 0kb XDS file.
And to top it off, our backup coincidentally failed just last night...
So... does Ext Designer have an option to re-create forms from .js code that was exported? Nope... guess I'm re-creating the whole project... there goes days of work.
It's no excuse for Designer but please please use source control
Had all our PHP code under source control, but always assumed that the XDS was a binary file.
It is now though
Unfortunately I have to use Visual Studio 2010 (for .NET service development) and Team Foundation Server for source control, which means that incorporating Ext Designer-generated content in my Solution/Project isn't seen by Microsoft's source control. I hope they make it so that you can say "everything in the solution directory, no matter how it gets there, is part of source control" one day, but for now, they don't. I don't suppose you have seen this, or know of a way around it, or have any clients with similar problems?
Originally Posted by Phil.Strong
At the moment I'm periodically zipping the entire solution folder and copying that to my network drive (which is backed up). It's not pretty, but at least it's backup. I just wish TFS in Visual Studio was a bit more configurable and didn't expect you to do everything their way.
Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection
can never be obtained...
When in doubt, check the d4mn source code!
And here are my terms...
- I don't care if you use my source code. (Known as "Code.")
- I don't care if I get any monetary compensation.
- I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.
- Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.
- By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.
- You are welcome to change and improve the Code to best meet your needs.
- I don't care if you use the Code in a commercial or open-source project.
- You are not required to contact me prior to using the Code.
Of course you can back it up using TFS. TFS power toys
Windows Shell Extensions
I have tried that but it's not much of an improvement. You have to remember to manually add things generated by Ext Designer, and if you make the mistake of deleting a file in explorer and not Visual Studio (if you no longer want an Ext JS class or something), you're in for a world of error messages as punishment for thinking outside the box. Unless you're prepared to be joined at the hip to Visual Studio, your life is going to be painful with TFS, sadly. So the old-fashioned periodic zip files will have to do until Microsoft improve their source control tools to be more accomodating of non-drones.