* Set up CI with Azure Pipelines
[skip ci]
* Update publishSqlCoreProject.yml for Azure Pipelines
* Update publishSqlCoreProject.yml for Azure Pipelines
* Update publishSqlCoreProject.yml for Azure Pipelines
* Update publishSqlCoreProject.yml for Azure Pipelines
* Update publishSqlCoreProject.yml for Azure Pipelines
* Updating json rpc target framework
* Fixing packages to pack
* fixing pattern
* Fixing project pattern
* adding versioning schema
* fixing versioning scheme
* fixing nuget package name
* adding name
* removing var
* Fixing stuff
* Fixing stuff
* Fixing stuff
* Fixing build name
* removing build name
* fixing name
* fixing stuff
* fix pattern
* Fixing stuff
* Fixing feed
* Fix stuff
* Fixing feed
* fixing proj name
* Fixing stuff
* Fixing netframework version
* Fixing target framework
* Adding target framework to dependency
* Fixing frameworks
* adding net7.0
* adding flag
* Fixing target frameworks and making code compatible with lang version
* fixed flag
* Fixing assembly name
* Adding hosting in nuget package
* Fixing tests
* Moving steps to its main pipeline
* only releasing when release is true
* Fixing build scripts
* Adding version to csproj for packaging
* adding version
* Fix dirs
* Adding version number to right prop group
* Adding necessary dis
* Fixing build number
* fixing datatype
* Using different var
* Removing unused yml
* Adding back nullables to hosting
* Adding back more nullables
* adding back more nullables
* moving some props to dir level
* Fixing tests
* Removing dup properties
* Supporting different target frameworks in hosting
* Removing additional setting in csproj
* signing sql core dll in publish
* Fixing version setting
* Adding to build
* Added signing and packaging flag
* Fixing file pattern
* adding network file validator contract
* updating to dotnet 5
* reverting change in pipeline
* updating target framework to 5.0
* updating srgen and using target framework var
* reverting srgen back to 3.1
* Adding dotnet 3.1 to build
* Fixing task def
* removing global json
* updating other 3.1 refs to 5.0
* removing netcore folder from build.cake
* Moving and renaming dotnet 3.1 task
* Update form .NET Core 2.2 to .NET Core 3.1
- Global variable for projects
- Change TFMs from netcoreapp2.2 to netcoreapp3.1
- Update global.json
- Update build.json
- Remove direct framework cake TestCore task
- Update travis dotnet version
- Update azure pipline file
- Update vscode launch.json
* Add Central Package Management
* Fix xUnit Breaking Change for MemberData type
* Fix xUnit breaking change for duplicate test method name
* Fix Rang/Index type conflict with System.Rang/Index
* Update vscode tasks.json
* Change serviceHostExecutable path in ServiceTestDriver.cs
* Downgrade SDK version (https://github.com/appveyor/ci/issues/3440)
- Appveyor hasn't installed latest SDK therefore I downgrade it until they install it.
* Dump Microsoft.SqlServer.DACFx
* Initial .net core 2.0 conversion
* Convert a few more projects to .net core 2.0
* Convert a few more projects to .net core 2.0
* Fix build.cmd errors
* Add mising nuget package
* Remove dead code
* Add checked in references to workaround nuget package issues
* Update SLN file to refer to correct csproj files
* Rename applications to workaround .net core tooling bug
* Update nuget package with SQL Parser changes
* Add PreserveCompliationContext to avoid MEF bug
* Update smo version to pickup .net core 2 changes
* Pickup latest SMO changes to fix merge break
* Actually pickup correct SMO binaries
* Add support for SLES 12.2
* Fix break running archiving on Linux
* Revert "Add support for SLES 12.2"
This reverts commit 95cdb6d0e35a425be5c0081345d214079cbdc3db.
* Update to latest SMO build
* Install .Net Core 2 during install phase
* Move .Net Core install
* Try to reference dotnet.exe directly
* Fix code coverage script for CSPROJ instead of project.json
* Turn off test that is unreliable in AppVeyor builds.
* Fix appveyor.yml line feed.
* Turn off another flaky test failing in AppVeyor
* Port over initial block of create db implementation
* Test case placeholder
* In-progress work
* Stage changes to other machine
* Add database prototype strings
* Stage changes to other machine
* Stage changes
* Hook the database info into capabilities discovery
* Stage changes
* Update SMO to latest from ssms_main
* Various clean-ups
* Update localization files
Update the ScriptingService to expose new scripting JSON-RPC APIs that use the SqlScriptPublishModel for script generation.
The SqlScriptPublishModel is the model behind the SSMS scripting wizard. To enable scripting for CLI tools, we've ported SqlScriptPublishModel to .NET Core. The SqlScriptPublishModel wraps the SMO scripting APIs for .sql script generation.
1) Added three new requests to the ScriptingService: ScriptingRequest, ScriptingListObjectsRequest, ScriptingCancelRequest.
2) Generating scripts are long running operations, so the ScriptingRequest and ScriptingListObjectsRequest kick off a long running scripting task and return immediately.
3) Long running scripting task reports progress and completion, and can be cancelled by a ScriptingCancelRequest request.
4) Bumped the SMO nuget package to 140.17049.0. This new version contains a signed SSMS_Rel build of SMO with the SqlScriptPublishModel.
5) For testing, adding the Northwind database schema
TODO (in later pull requests)
1) Integrate the new ScriptingService APIs with the ConnectionService
2) Integrate with the metadata support recently added
* Bump SMO bits to align with 17.0 RC3 release
* Add updated SMO binary
* Fix formatter failures caused by SqlProc breaking changes
- Changes to SqlProcedureDefinition subclasses mean that the definition starts at "Create Procedure" instead of after it. This highlighted an issue where the prefix region handling was via comma separated list (which adds newlines to the prefix region) instead of newline separated list (which does not).
- Changed the structure to use the 2 different formatters for relevant regions, and verified all tests now pass.
- Also removed unnnecessary Export clause from the SqlTableDefinitionFormatter, since this was spotted during debugging
* Fix sample project.json dependencies
- Fix up the dependencies in our samples as this was failing the build on TravisCI. Should consider in the future whether or not we want to exclude these from CI runs, but for now the benefit is that we're forced to keep the samples up to date.
This is a documentation-only update so automerging. Please review the commit if there are any follow-ups requested.
* Update .gitignore for docfx genertated files
* Update documenation (part 1)
* Update docs and add some samples
* More doc updates
