Modframe 2.3.0

Updates:-

• updated the .NET Core version to now be 2.1, the previous update showed 2.1.4 which was not correct, this was the SDK version not the runtime version of 2.0.

• updated the .NET Framework version to now be 4.7.2 by default

• updated the babel packages and changed it to standard version packages due to breaking changes in the new beta versions.

• made the decision to remove plugins.json files from layouts, modules and global. This decision was made as it encouraged duplication of code and makes it less flexible in the future for moving to different package managers.

• removed the gulp-newer that was used in the con and min pipeline, this might slightly increase the times but the plugin was only working from a timestamp on modification, if you deleted or added a new file that timestamp was not being picked up and thus ignored.

ModFrame 2.2.0

Updates:-

• Updated the project name versions
• Upgraded Bootstrap to stable 4.0.0
• Upgraded FontAwesome to 5.0.3
• Upgraded jQuery to 3.3.1
• Upgraded popper.js to 1.12.9 (Bootstrap requirement)
• Adjusted the second layer font icons to use the new FontAwesome format
• Added Vue.js
• Added a basic Vue.js example to the front page

ModFrame 2.1.0

Updates:-

• Removed the babel-preset-{versions} due to future deprecation and replaced them with the new @babel/preset-env which still does all the same stuff and more.

• Updated the gulp-babel version so it now uses @babel/core so we can remove the babel-core dependency

• Added a required framework version of 4.5 for ModFrame

• Updated the default .NET Core (Full Framework) template to target .NET 4.7.1

• Updated the .NET Core libraries to 2.02 and for .NET Core (.NET Core) the all bundle of 2.03 (2.1.4 SDK)

ModFrame 2.0.0

Updates:-

• The documentation has been finalized for this version and is now ready to be used for full guidance

• A "README.txt" file has been added to the project template which has links to the repository and documentation

• Fixed a bug in the Module View extension method where it was not allowing a group to be supplied this breaking the ability to import extra module views

• Fixed a bug in the Module View extension method where it was not allowing a model to be supplied

• Fixed a bug in the Global View extension method where it was not allowing a model to be supplied

ModFrame 1.9.0

Updates:-

• Slightly changed the build process to fix a bug where the *.csproj file was being added into ModFrame templates from the original project
• Changed the location of the LICENSE file to be inside the ModFrame folder
• Adjusted folders and filenames to the correct standards
• Prefixed all ModFrame gulp tasks with MF, so if you want to add your own it does not get confusing
• Moved the startup ModFrame configuration setup directly into the startup.cs file to make to more adaptable for different people’s requirements
• Added the files folder to layouts, globals and modules which syncs any files within that folder to the wwwroot/files folder
• Added the new gulp files tasks for making this process automatic
• Fixed a bug in the web.config where some vital details where missed out when publishing to a production IIS instance
• Fixed a bug in the .csproj where when publishing views where being compiled into a DLL and breaking ModFrame
• Fixed a bug with the default bootstrap 4 layouts not having the correct meta heading tags for enabling responsive design on mobiles
• Fixed a bug where the assembly names where always ModFrame rather than the project name selected
• Fixed a bug in the vstemplate to now not include the vstemplate file and the template icon file in the real projects

ModFrame 1.8.0

Updates:-

• added the application insight function commented out in the programs.cs file in case anyone wants to use it after configuring application insight for their project.

• added a web.config and another parameter to the core upload size so the default fileupload is 2GB if using IIS

• fixed a bug where certain single files being watched by Chokidar would unlink, have used the guidance on the git issue page to resolve this issue

• changed the packages task to now use pump so gulp is no longer caching files and the process if more efficient

• added bower and npm commands after the packages task has finished running to update or remove installs

• updated all the npm packages to their latest version

• have changed all bower references in plugin.json files to now hold the version in the name for easier multiple version support

• have changed the layouts and default loading package to now use Bootstrap 4.0.0-beta by default

ModFrame 1.7.0

Updates:-

• add babel into the core minification and concatenation process to allow ES conversion functionality so you can now write ES2015, ES2016 and ES2017 JS throughout ModFrames JS folders and it will convert it to normal JS.

ModFrame 1.6.0

Updates:-

• Modified the core concatenation and minifications process to use pump rather than the gulp pipes, this way we can output any kind of JS uglification error and its location while preventing the watchers from closing down due to the error.

• Modified how packages "plugins.json" get JSON.Parse so we can now display the error and its location while preventing the watchers from closing down due to the error.

ModFrame 1.5.0

Updates:-

• fixed a bug with the new package task and internal gulp plugin, originally they used nodes require() function to get the json object but as its dynamic content and a watcher does not shutdown its thread, node was retaining the first cache of the require() function usage on the dynamic file changes.

ModFrame 1.4.0

Updates:-

• optimized the way gulp functionality processes concatenation and minification

• added SASS and Less support (.scss and .less) in the minification and concatenation process for any ModFrame css folder

• removed the bower gulp task and added a packages task instead

• npm has also been added to the support from the plugins.json files

• changed the structure of the plugins.json file to now support both bower and npm dependencies

• added formatting to the processed bower.json and packages.json output after the new packages task is run

• changed a bug in the name for the default bower.json name attribute

• updated it so by default the plugins folder and its two sub directories are now present on a new project by default

• changed the npm packages to not be under dev dependencies but normal dependencies in the packages.json file by default