Hello GitHub

Author: HowardWolosky

.editorconfig

@@ -0,0 +1,11 @@
+## IDE-independent coding style via EditorConfig: http://editorconfig.org/
+
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+end_of_line = crlf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true

.gitattributes

@@ -0,0 +1,63 @@
+###############################################################################
+# Set default behavior to automatically normalize line endings.
+###############################################################################
+* text=auto
+
+###############################################################################
+# Set default behavior for command prompt diff.
+#
+# This is need for earlier builds of msysgit that does not have it on by
+# default for csharp files.
+# Note: This is only used by command line
+###############################################################################
+*.cs     diff=csharp
+
+###############################################################################
+# Set the merge driver for project and solution files
+#
+# Merging from the command prompt will add diff markers to the files if there
+# are conflicts (Merging from VS is not affected by the settings below, in VS
+# the diff markers are never inserted). Diff markers may cause the following 
+# file extensions to fail to load in VS. An alternative would be to treat
+# these files as binary and thus will always conflict and require user
+# intervention with every merge. To do so, just uncomment the entries below
+###############################################################################
+*.sln       merge=binary
+*.csproj    merge=binary
+*.vbproj    merge=binary
+*.vcxproj   merge=binary
+*.vcproj    merge=binary
+*.dbproj    merge=binary
+*.fsproj    merge=binary
+*.lsproj    merge=binary
+*.wixproj   merge=binary
+*.modelproj merge=binary
+*.sqlproj   merge=binary
+*.wwaproj   merge=binary
+
+###############################################################################
+# behavior for image files
+#
+# image files are treated as binary by default.
+###############################################################################
+*.jpg   binary
+*.png   binary
+*.gif   binary
+
+###############################################################################
+# diff behavior for common document formats
+# 
+# Convert binary document formats to text before diffing them. This feature
+# is only available from the command line. Turn it on by uncommenting the 
+# entries below.
+###############################################################################
+*.doc   diff=astextplain
+*.DOC   diff=astextplain
+*.docx  diff=astextplain
+*.DOCX  diff=astextplain
+*.dot   diff=astextplain
+*.DOT   diff=astextplain
+*.pdf   diff=astextplain
+*.PDF   diff=astextplain
+*.rtf   diff=astextplain
+*.RTF   diff=astextplain

.gitignore

@@ -1,4 +1,4 @@
-## Ignore Visual Studio temporary files, build results, and
+## Ignore Visual Studio temporary files, build results, and
 ## files generated by popular Visual Studio add-ons.
 ##
 ## Get latest from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore
@@ -24,14 +24,11 @@ bld/
 [Oo]bj/
 [Ll]og/
 
-# Visual Studio 2015/2017 cache/options directory
+# Visual Studio 2015 cache/options directory
 .vs/
 # Uncomment if you have tasks that create the project's static files in wwwroot
 #wwwroot/
 
-# Visual Studio 2017 auto generated files
-Generated\ Files/
-
 # MSTest test Results
 [Tt]est[Rr]esult*/
 [Bb]uild[Ll]og.*
@@ -45,29 +42,20 @@ TestResult.xml
 [Rr]eleasePS/
 dlldata.c
 
-# Benchmark Results
-BenchmarkDotNet.Artifacts/
-
 # .NET Core
 project.lock.json
 project.fragment.lock.json
 artifacts/
 **/Properties/launchSettings.json
 
-# StyleCop
-StyleCopReport.xml
-
-# Files built by Visual Studio
 *_i.c
 *_p.c
 *_i.h
 *.ilk
 *.meta
 *.obj
-*.iobj
 *.pch
 *.pdb
-*.ipdb
 *.pgc
 *.pgd
 *.rsp
@@ -105,9 +93,6 @@ ipch/
 *.vspx
 *.sap
 
-# Visual Studio Trace Files
-*.e2e
-
 # TFS 2012 Local Workspace
 $tf/
 
@@ -128,10 +113,6 @@ _TeamCity*
 # DotCover is a Code Coverage Tool
 *.dotCover
 
-# AxoCover is a Code Coverage Tool
-.axoCover/*
-!.axoCover/settings.json
-
 # Visual Studio code coverage results
 *.coverage
 *.coveragexml
@@ -167,7 +148,7 @@ publish/
 # Publish Web Output
 *.[Pp]ublish.xml
 *.azurePubxml
-# Note: Comment the next line if you want to checkin your web deploy settings,
+# TODO: Comment the next line if you want to checkin your web deploy settings
 # but database connection strings (with potential passwords) will be unencrypted
 *.pubxml
 *.publishproj
@@ -180,11 +161,11 @@ PublishScripts/
 # NuGet Packages
 *.nupkg
 # The packages folder can be ignored because of Package Restore
-**/[Pp]ackages/*
+**/packages/*
 # except build/, which is used as an MSBuild target.
-!**/[Pp]ackages/build/
+!**/packages/build/
 # Uncomment if necessary however generally it will be regenerated when needed
-#!**/[Pp]ackages/repositories.config
+#!**/packages/repositories.config
 # NuGet v3's project.json files produces more ignorable files
 *.nuget.props
 *.nuget.targets
@@ -202,7 +183,6 @@ AppPackages/
 BundleArtifacts/
 Package.StoreAssociation.xml
 _pkginfo.txt
-*.appx
 
 # Visual Studio cache files
 # files ending in .cache can be ignored
@@ -221,10 +201,6 @@ ClientBin/
 *.publishsettings
 orleans.codegen.cs
 
-# Including strong name files can present a security risk 
-# (https://github.com/github/gitignore/pull/2483#issue-259490424)
-#*.snk
-
 # Since there are multiple workflows, uncomment next line to ignore bower_components
 # (https://github.com/github/gitignore/pull/1529#issuecomment-104372622)
 #bower_components/
@@ -239,8 +215,6 @@ _UpgradeReport_Files/
 Backup*/
 UpgradeLog*.XML
 UpgradeLog*.htm
-ServiceFabricBackup/
-*.rptproj.bak
 
 # SQL Server files
 *.mdf
@@ -251,7 +225,6 @@ ServiceFabricBackup/
 *.rdl.data
 *.bim.layout
 *.bim_*.settings
-*.rptproj.rsuser
 
 # Microsoft Fakes
 FakesAssemblies/
@@ -263,6 +236,9 @@ FakesAssemblies/
 .ntvs_analysis.dat
 node_modules/
 
+# Typescript v1 declaration files
+typings/
+
 # Visual Studio 6 build log
 *.plg
 
@@ -302,9 +278,6 @@ __pycache__/
 # tools/**
 # !tools/packages.config
 
-# Tabs Studio
-*.tss
-
 # Telerik's JustMock configuration file
 *.jmconfig
 
@@ -314,17 +287,15 @@ __pycache__/
 *.odx.cs
 *.xsd.cs
 
-# OpenCover UI analysis results
-OpenCover/
-
-# Azure Stream Analytics local run output 
-ASALocalRun/
-
-# MSBuild Binary and Structured Log
-*.binlog
+# Calculator specific
+Generated Files/
+# Don't ignore anything under SpkgDefs or TrexDefs
+!/SpkgDefs/**
+!/TrexDefs/**
+!/build/config/TRexDefs/**
 
-# NVidia Nsight GPU debugger configuration file
-*.nvuser
+# Localized strings
+# LCT files are loc system artifacts that we don't want in our repo.
+*.lct
 
-# MFractors (Xamarin productivity tool) working folder 
-.mfractor/
+WorkspaceInfo.xml

CODE_OF_CONDUCT.md

@@ -0,0 +1,6 @@
+# Code of Conduct
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
+or contact [[email protected]](mailto:[email protected]) with any additional questions or
+comments.

CONTRIBUTING.md

@@ -0,0 +1,96 @@
+# Contributing to Calculator
+The Calculator team encourages community feedback and contributions. Thank you for your interest in
+making Calculator better! There are several ways you can get involved.
+
+## Reporting issues and suggesting new features
+If Calculator is not working properly, please file a report in the [Feedback Hub](https://insider.windows.com/en-us/fb/?contextid=130&newFeedback=True).
+Feedback Hub reports automatically include diagnostic data, such as the version of Calculator
+you're using.
+
+We are happy to hear your ideas for the future of Calculator. Check the
+[Feedback Hub](https://insider.windows.com/en-us/fb/?contextid=130) and see if others have
+submitted similar feedback. You can upvote existing feedback or submit a new suggestion.
+
+We always look at upvoted items in Feedback Hub when we decide what to work on next. We read the
+comments in both Feedback Hub and GitHub, and we look forward to hearing your input. Remember that
+all community interactions must abide by the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Finding issues you can help with
+Looking for something to work on?
+[Issues marked *up for grabs*](https://microsoft.com/#TODO_MIGRATE_THIS_LINK_AFTER_GITHUB_MIGRATION)
+are a good place to start.
+
+Another way you can help is by reproducing issues others have reported.
+[Issues marked *more info needed*](https://microsoft.com/#TODO_MIGRATE_THIS_LINK_AFTER_GITHUB_MIGRATION)
+don't have all the information needed to take action. You can try to reproduce the issue on your
+machine and add more details so we can take action on the report.
+
+## Contributions we accept
+We welcome your contributions to the Calculator project, especially to fix bugs and to make
+improvements which address the top issues reported by Calculator users.
+
+We have a high bar for new features and changes to the user experience. We prefer to evaluate
+*prototypes* to ensure that the design meets users' needs before we start discussing implementation
+details and reviewing code. We follow a [user-centered process for developing features](docs/NewFeatureProcess.md).
+New features need sponsorship from the Calculator team, but we welcome community contributions at
+many stages of the process.
+
+## Making changes to the code
+
+### Preparing your development environment
+To learn how to build the code and run tests, follow the instructions in the [README](README.md).
+
+### Style guidelines
+The code in this project uses several different coding styles, depending on the age and history of
+the code. Please attempt to match the style of surrounding code as much as possible. In new
+components, prefer the patterns described in the [C++ core guidelines](http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines)
+and the [modern C++/WinRT language projections](https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/).
+
+### Testing
+Your change should include tests to verify new functionality wherever possible. Code should be
+structured so that it can be unit tested independently of the UI. [Manual test cases](docs/ManualTests.md)
+should be used where automated testing is not feasible.
+
+### Git workflow
+Calculator uses the [GitHub flow](https://guides.github.com/introduction/flow/) where most
+development happens directly on the `master` branch. The `master` branch should always be in a
+healthy state which is ready for release.
+
+If your change is complex, please clean up the branch history before submitting a pull request.
+You can use [git rebase](https://docs.microsoft.com/en-us/azure/devops/repos/git/rebase#squash-local-commits)
+to group your changes into a small number of commits which we can review one at a time.
+
+When completing a pull request, we will generally squash your changes into a single commit. Please
+let us know if your pull request needs to be merged as separate commits.
+
+## Submitting a pull request and participating in code review
+Writing a good description for your pull request is crucial to help reviewers and future
+maintainers understand your change. More detail is better.
+- [Link the issue you're addressing in the pull request](https://github.com/blog/957-introducing-issue-mentions).
+- Describe *why* the change is being made and *why* you've chosen a particular solution.
+- Describe any manual testing you performed to validate your change.
+
+Please submit one pull request per issue. Large pull requests which have unrelated changes can be
+difficult to review.
+
+After submitting a pull request, members of the calculator team will review your code. We will
+assign the request to an appropriate reviewer within two days. Any member of the community may
+participate in the review, but at least one member of the Calculator team will ultimately approve
+the request.
+
+Often, multiple iterations will be needed to responding to feedback from reviewers. Try looking at
+[past pull requests](https://microsoft.com/#TODO_MIGRATE_THIS_LINK_AFTER_GITHUB_MIGRATION) to see
+what the experience might be like.
+
+## Contributor License Agreement
+Before we can review and accept a pull request from you, you'll need to sign a Contributor License
+Agreement (CLA). The CLA ensures that the community is free to use your contributions. More
+information about the agreement is available on the [Microsoft web site](https://cla.opensource.microsoft.com/).
+Signing the CLA is an automated process, and you only need to do it once for Microsoft projects on
+GitHub.
+
+You don't need to sign a CLA until you're ready to create a pull request. When your pull request is
+created, it is classified by a bot. If the change is trivial (i.e. you just fixed a typo) then the
+bot will label the PR `cla-not-required`. Otherwise, it's classified as `cla-required`. In that
+case, the system will also tell you how you can sign the CLA. Once you have signed a CLA, the
+current and all future pull requests will be labeled as `cla-signed`.