Skip to content
This repository was archived by the owner on Sep 4, 2019. It is now read-only.

Merge Next into Master to prepare for build#674

Open
dbrgss wants to merge 877 commits into
masterfrom
next
Open

Merge Next into Master to prepare for build#674
dbrgss wants to merge 877 commits into
masterfrom
next

Conversation

@dbrgss

@dbrgss dbrgss commented Jan 29, 2015

Copy link
Copy Markdown
Collaborator

No description provided.

Now all is provided by the package resources, no need to duplicate the
same descriptions all over across .vsdir files in different folders.
It is enough to specify any number of the template files via 'FILE' custom-property of
.vsz file. Also the path supports two markers '->' and '#>' to override
whole name and extension only of developer supplied item name.

Sample of .vsz file:

VSWizard 7.0
Wizard={0cb934ba-06c8-4919-9498-bc6517940bcd}
Param="FILE = any/file/path.xml -> 'this name instead' "
Param="FILE = any/file/path.xml #> .txt "
Also improved existing templates itself.
As for now the wizard engine can:
 * create multifile project items
 * create multifile project targetting directly BlackBerry platform

Engine uses some customizable simple rules to rename and put in proper
folders depenant files and automatically update their content.
Each supported version of Visual Studio exposed dedicated BlackBerry
Project and ProjectItems entries. Still need more content there, but the
general idea (like custom icons and custom project properties per VS
version) is working fine.
It mostly adds empty, NativeCore and Hello-World Cascades projects.
Still missing better prototypes for Cascades and Headless application.
Improved PuppetMaster wizard-enging to allow renaming project templates the
same way project-items are processed. Now it's possible to have multiple
projects generated automatically inside the solution, that share the same
'core' name part, specified by developer using Visual Studio 'New Project'
dialog.
Also some engine variable registered for QML in Card template.
It works now out-of-the-box!
All NativeCore projects build into the same folders as the other Visual
Studio versions. Those projects just manually overwrite the $(OutPath).
Newer Visual Studios can do it automatically, when the $(TargetCPU) variable
value changes.
phofman and others added 4 commits January 14, 2015 18:34
Battlefield v3.3.1 integration
Modified the Help Links changes proposed by docs.
Fixed minor issue with Add Target dialog.
dbrgss and others added 25 commits January 29, 2015 11:35
Made various working changes proposed by docs.
…oing a package build.bat.

Modified the project files to copy the Template files to the buildresults folder.
Modify code to copy Template files for install.
1) Removed the Remove button for Debug Tokens.  Left the code behind as this might be re-added if/when the underlying NDK API is repaired.
2) Multiple wording changes for the docs group.
3) Fixed the enable/disable code for the Unregister button.
To avoid messing up forks, that don't need developer tags from upstream.
To follow new values from VS2013 version.
Using letter 'B' was on a collision course with standard 'BUILD' menu.
Fixed issue: blackberry/VSPlugin/#681
This could happend due to invalid syntax or similar.
Returning E_FAIL to VisualStudio, that handles displaying error message.

Issue: blackberry/VSPlugin/#676
_dte.Solution.SaveAs() call internally presents UI to ask the user, where to
store the solution file. If user presses [Cancel] button, it will throw an
exception, what improperly skipped adding files into the project.

Issue: blackberry/VSPlugin/#680
New developers without anything initialized yet could not perform some
basic actions (like list processes, navigate file-system, etc.) of the
device until they deployed their first application, what effectively
generated mandatory SSH public/private key pair.

Issue: blackberry/VSPlugin/#702
Those menu options were always enabled, now they reflect the device's connectivity state.

Issue: blackberry/VSPlugin/#703
Executed just after unregistration, that switched certificate's file name
to null causing later an exception.

Issue: blackberry/VSPlugin/#684
Issues: blackberry/VSPlugin/#692 blackberry/VSPlugin/#673
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants