-
Notifications
You must be signed in to change notification settings - Fork 2k
Get SQL Server working with ASP.NET tests on Windows #336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This includes: * install-client.ps1: a PowerShell script to be run on a Windows Server box to download and install SQL Server. * config/create-sqlserver*.sql: SQL Server T-SQL scripts to create a database user and populated database. * Initial changes to allow sqlserver as a provider for AdoController.cs. This is somewhat incomplete and needs work: * How to run the T-SQL scripts if they haven't been pulled down from Git? * Need wrk or something similar for Windows. * How to get the python script on the server to run remote commands on the client database box?
1. Add setup-sqlserver-bootstrap.ps1 that can be run from the web. 2. Run T-SQL scripts at the end of setup-sqlserver.ps1. 3. Make T-SQL scripts delete stuff if necessary.
1. Add aspnet-sqlserver-raw and aspnet-sqlserver-entityframework tests. 2. Don't share DbParameter object between two SqlCommand objects because SqlCommand objects. 3. Get SQL Server working with the Entity Framework. 4. Tidy up T-SQL. 5. Fix typo in setup-sqlserver-bootstrap.ps1 with config path. 6. Complete SQL Server setup and configuration in setup-sqlserver.ps1.
Wow, impressive work, @MalcolmEvershed. Thank you very much for this! |
Since the column is nvarchar, the string constants that are inserted should be prefixed with N like N'foo' instead of 'foo'. This fixes the Japanese string.
SQL Server is now supported via the SqlClient provider.
michaelhixson
added a commit
that referenced
this pull request
Jul 16, 2013
Get SQL Server working with ASP.NET tests on Windows
This is awesome. Thanks @MalcolmEvershed. |
michaelhixson
added a commit
that referenced
this pull request
Oct 12, 2013
Get SQL Server working with ASP.NET tests on Windows
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With @pdonald's advising, I got the SQL Server stuff done. I've never tested this on Amazon EC2, but I think it'll probably work.
Follow the instructions in
README.md
to setup the SQL Server box, then userun-tests.py -d
to point to it foraspnet-sqlserver-raw
andaspnet-sqlserver-entityframework
.CC: @bhauer