rantanen / m-files-sdk Goto Github PK

The UI control library is probably the most common external library utilized with the references.

Creating a version of the library that contains the appdef.xml (or libdef.xml) would make this easier.

Add editorconfig configuration to standardize the formatting styles for code.

When referencing libraries, there should be a way for Visual Studio to display IntelliSense for them.

See http://wix.sourceforge.net/manual-wix3/vs_xsd_vsixpackage.htm

Create profile setting for different M-Files versions. This would enable/disable support for specif features.

A concrete example is 9.0.3372.x profile disabling the msbuild framework library as 9.0.3372.x branch doesn't execute the global scope.

When cleaning the project, the process should also remove the application from the client/apps folder.

Add JavaScript IntelliSense documentation for the base APIs that M-Files provides.

Note: This probably needs support M-Files.

At minimum add a "M-Files build tasks have been installed successfully." message.

It is a tad too easy to leave pile of work-in-progress applications into the vault.

Add a button to the debug screen which opens the installation path would so the user can view those and remove the unneeded ones easily.

The style used in M-Files samples uses XML comments:

function x() {
   /// <summary>Function X</summary>
   /// <return>Return value</return>
   return null;
}

The main reason for this is the IntelliSense support. However there are references (https://twitter.com/mkristensen/statuses/245603173404917760) that JSDoc might make it to VS2012 at some point.

If JSDoc receives equal IntelliSense support as the current XML comments, then the question becomes whether being able to comment anonymous functions used as method parameters is worth it over more standardized and easier to read format.

The extension shouldn't be using VS2012 specific APIs so it should be possible to make it compatible with the VS2010 SDK.

Dashboards are reloaded even without the logout/login cycle. Being able to opt out of it would remove some of the delays involved in launching these for testing.

Currently if the local client doesn't have the vault used for debugging the application the launch (F5) fails and the user has to go to the Debug properties to change the vault. It would be nicer to the user if Visual Studio would ask the user for a new vault with a modal dialog in this case - providing a list of the currently installed vaults to choose from and mayhaps a checkbox for "Save this vault in the project settings".

Set up CC.Net or similar and include build time in the version string: major.minor.YYMMDD.build

TypeScript support would be a great feature and probably easy enough to implement. The main problem with this is that it most likely requires global scope processing which isn't implemented yet.

Add a library project template and library option to the projects.

The MSBuild task should generate (and understand) libdef.xml definition files for these project. This makes the distinction of an application and a library clearer and accidentally deploying a library won't cause any problems as it won't get loaded by the client.

Due to lack of documentation there is a large amount of experimental and badly documented code in the source tree. Clean it up.

Support specifying Minify properties on .js and .css files and run minifier before zipping these.

The property should have 3 values: true, false and default. The "default" value reads the minify settings from the project configuration. By default 'Debug' configuration should skip minify while 'Release' configuration should perform it.

Based on an installed version there is no way to tell which revision it came from.

Include current git revision in the build artifacts.