Comment on page
Steps to bootstrap your project in 3 minutes
- Create a new Visual Studio solution and add a new WPF (.NET Core 3) application project;
- Delete the default MainWindow.xaml;
- Edit the app.xaml file to remove the
- Add a
Presentationfolder to the project;
Presentationis the default location, based on conventions, where Radical looks for Views and ViewModels;
- Create 2 new items in the
- A WPF window named MainView.xaml (*View is important for the default conventions);
- A class MainViewModel (<ViewName>ViewModel is important for the default conventions);
- In the app.xaml.cs add a single line of code:
public partial class App : Application
Press F5 and you are up & running: the
MainViewwindow will be shown. The following things happen:
- The application boots
- All the default and required services (for MVVM and UI Composition) are wired into the IoC container (using
MainViewis designed as the main window
- At boot time the
MainViewis resolved and using the conventions engine the
MainViewModelis setup and set as the
- Finally the
Radical follows a set of rules to prepare and publish releases:
- Define the milestone;
- Define an issue for everything that gets touched;
- Associate the issue to the milestone;
- Associate a commit with an issue and close it;
- Publish the release associated to the milestone;
Your contributions to Radical are very welcome. If you find a bug, please raise it as an issue. Even better fix it and send a pull request. If you like to help out with existing bugs and feature requests just check out the list of issues and grab and fix one:
- If you find a bug, please raise it as an issue, even better followed by a pull request.
- This project uses Release Flow for pull requests. So if you want to contribute, fork the repo, create a descriptively named branch off of master (ie: portable-class-library-support), fix an issue, run all the unit tests, and send a PR if all is green.
- Please rebase your code on top of the latest commits. Before working on your fork make sure you pull the latest so you work on top of the latests commits to avoid merge conflicts. Also before sending the PR please rebase your code as there is a chance there have been new commits pushed after you pulled last.
- We will only merge PR that could be automatically merged.
Radical follows the following versioning scheme:
major - version when you make incompatible API changes.
minor - when you add functionality in a backwards-compatible manner.
patch - when you make backwards-compatible bug fixes.
extensions - pre-release extensions
version - pre-release version
The Radical source code includes several samples that are divided per scope and technology, samples are available in the documentation repository: https://github.com/RadicalFx/documentation/tree/master/samples
All samples are constantly under heavy development and are also used to test Radical features.
Radical uses MyGet to publish unstable releases during development, to use the unstable feed:
- create a
nuget.configfile in the same folder as your solution folder
- add the following content to the configuration file:
<?xml version="1.0" encoding="utf-8"?>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
<add key="Radical Unstable" value="https://www.myget.org/F/radical-unstable/api/v3/index.json" />
- close and reopen the solution
By going to the Manage Nuget Packages page of your solution, you'll now see a "Radical Unstable" option in the source selection dropdown. Do not forget to check the "prerelease versions" checkbox search setting.
Radical uses AppVeyor to host the build infrastructure. All active repositories are mapped to an AppVeyor project. Branches are configured so that Pull Requests require builds to be green to be merged. Each time a new PR is raised and/or each time a new commit is pushed to an existing PR a build is triggered and the build status is reported to GitHub. From AppVeyor build artfacts, such as Nuget packages, can be pushed to Myget or to Nuget, depending on their stability level. Builds are triggered also when a TAG is pushed. Usually a TAG identifies a stable build that will be released to Nuget.