* Revert "fixed perf tests and added more scenarios (#683)"
This reverts commit aa2b30f486.
* Revert "Switch to the unified SMO NuGet so all binaries are strong named and signed. (#682)"
This reverts commit 69961992bb.
* add string serialization
* add unadded file
* changed code to be testable, added test
* moved test to correct location
* change to send undefined rather than error if the serialization fails
* update request name
* Upgrade SMO packages to fix issue with scripting tables when Script Dependencies is true on the script options.
* use linux style import with case matching file name
* Remove XUnit warnings which clogged up output
* Use default namespace to fix loc lookup errors
- Fixed errors due to localization change
- Also removed internals visible attribute that could cause subtle issues where the hosting service doesn't work for other apps if things change
* Add CI build and test for new projects
* Up version number so we can pick up fix in nuget packages
* Use netstandard for coreservices DLL
- This is possible thanks to recent updates that target SMO bits using netstandard
* Fix localization failure during dotnet pack
- Namespace changes on SRGen, so updated references to accept the name change
* Port v2 of Hosting service to SqlToolsService
- Renamed project to .v2 so that existing hosted service isn't impacted
- Copied over the CoreServices project which contains ConnectionServiceCore and other reusable services for anything interacting with MSSQL
- Ported unit test project across and verified tests run.
* Nuget package support for reusable DLLs
* Use 1.1 version per Karl's suggestion
* Use correct license URL and project URL
* Use new SMO packages
* Add IncludePassword flag to get connection string method
* Override connection application name
* Fix typo
* Fix test break
* Use ****** as password placeholder
* fixed bug where execution time was wrong for multiple batches
* fixed bug where multiple execution would show wrong execution time
* simplified logic
* Fix GUID parse error breaking on-prem connections
- Fixes https://github.com/Microsoft/sqlopsstudio/issues/1896
- Verified this is only used in retry logic on Azure, so the fact it's failing on-prem isn't relevant. It's still unclear why in some cases the session ID is non-null but not a GUID.
* Added back logging if parse of the GUID fails
* added support for t-sql parse
* added syntax parse to language service instead
* fixed misleading error
* code review comments
* fixed run state logic
* Initial changes for adding lost event notifications
* Handling polling errors by notifying listeners
* Restructuring lost events & testing
* Minor fixes to tests
* Add back in filtering
* Changing how lost events are found
* Cleaning up tests
* Agent Proxy account WIP
* Fixup Credential create\update\delete handlers
* Use current user for test credential
* Cleanup and delete code
* Convert tabs to spaces
