I tried to use an SDK-style project of SQL Server Data-Tier Application. It feels really natural to use dotnet build and dotnet publish thanks to https://github.com/rr-wfm/MSBuild.Sdk.SqlProj
Best part is, that tSQLt framework can be delivered in a very convenient way, as a nuget package.
Example file Tests.csproj looks like this:
<Project Sdk="MSBuild.Sdk.SqlProj/2.0.0-beta.1">
<PropertyGroup>
<TargetFramework>net6.0</TargetFramework>
<SqlServerVersion>Sql150</SqlServerVersion>
</PropertyGroup>
<ItemGroup>
<ProjectReference Include="..\Code\Code.csproj" />
<PackageReference Include="tSQLt.2019" Version="1.0.7950.1808" />
</ItemGroup>
</Project>
where tSQLt.2019 is a name of nuget package. Yes, we would need a lot of packages for each SqlServerVersion.
I put the whole example here: https://github.com/cagrin/tSQLt-visual-studio-examples
What do you think about this SDK-style?
Could it be possible to release nuget packages of tSQLt framework?
I tried to use an SDK-style project of SQL Server Data-Tier Application. It feels really natural to use
dotnet buildanddotnet publishthanks to https://github.com/rr-wfm/MSBuild.Sdk.SqlProjBest part is, that tSQLt framework can be delivered in a very convenient way, as a nuget package.
Example file
Tests.csprojlooks like this:where
tSQLt.2019is a name of nuget package. Yes, we would need a lot of packages for each SqlServerVersion.I put the whole example here: https://github.com/cagrin/tSQLt-visual-studio-examples
What do you think about this SDK-style?
Could it be possible to release nuget packages of tSQLt framework?