DevAndy | Right Hand of the Head of Development

Integrations Test mit Dependency Injection MsTest v2 .Net Core 3.1

Möchte man einen Integrationstest schreiben und dabei dependency injection nutzen, muss man folgendermaßen vorgehen:

Im Besten Fall teilt ma die Ausführende Applikation z.B. Web Applikation, Console etc und eine Bibliothek.

In die Bibliothek kommt die Auslagerung der StartUp:

    public static class ServiceCollectionExtensions
    {
        public static void UseMyModule(this IServiceCollection services)
        {
            services.AddTransient<IMyClass, MyClass>();
        }
    }

public static class ServiceCollectionExtensions

{

public static void UseMyModule(this IServiceCollection services)

{

services.AddTransient<IMyClass, MyClass>();

}

Im Testprojekt wird eine Basis Klasse definiert, die dieses Modul einliest. Nun kann in CofigureServices services.UseMyModule() aufgerufen werden oder der Host selbst gebaut werden:

    [TestClass]
    public class BaseTestUnit {

        public static IHost Host { get; set; }        

        [AssemblyInitialize]
        public static void ClassInitialize(TestContext context) {
            Host = AssemblyInit(context);            
        }        

        public static IHost AssemblyInit(TestContext context) {

            var host = Microsoft.Extensions.Hosting.Host.CreateDefaultBuilder(new string[0])
                .ConfigureHostConfiguration(webHost =>
                {

                })
                .ConfigureAppConfiguration((hostContext, config) =>
                {
                    // AppSettings nach MachineName auslesen
                    config
                        .SetBasePath(System.IO.Directory.GetCurrentDirectory())
                        .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
                        .AddJsonFile($"appsettings.{hostContext.HostingEnvironment.EnvironmentName}.json", optional: true)
                        .AddJsonFile($"appsettings.{Environment.MachineName}.json", optional: true)
                        .AddEnvironmentVariables();
                })
                .ConfigureServices((hostContext, services) =>
                {
                    services.AddOptions();
                    services.Configure<Application.Configuration.Configuration>(hostContext.Configuration.GetSection("Section in AppSettings"));                    

                    NLog.Logger logger = NLog.LogManager.GetLogger("NLog Name");
                    services.AddSingleton(logger);

                    services.Configure((Localization.Configuration.LocalizationConfiguration options) => hostContext.Configuration.GetSection("Localization Section in AppSettings").Bind(options));
                    services.AddSingleton<Localization.ILocalizationService, Localization.LocalizationService>();

                    services.AddSingleton<IMyClass, MyClass>();
                });

            return host.Start();
        }

        public T GetService<T>() => (T)Host.Services.GetService(typeof(T));

    }

[TestClass]

public class BaseTestUnit {

public static IHost Host { get; set; }

[AssemblyInitialize]

public static void ClassInitialize(TestContext context) {

Host = AssemblyInit(context);

}

public static IHost AssemblyInit(TestContext context) {

var host = Microsoft.Extensions.Hosting.Host.CreateDefaultBuilder(new string[0])

.ConfigureHostConfiguration(webHost =>

{

})

.ConfigureAppConfiguration((hostContext, config) =>

{

// AppSettings nach MachineName auslesen

config

.SetBasePath(System.IO.Directory.GetCurrentDirectory())

.AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)

.AddJsonFile($"appsettings.{hostContext.HostingEnvironment.EnvironmentName}.json", optional: true)

.AddJsonFile($"appsettings.{Environment.MachineName}.json", optional: true)

.AddEnvironmentVariables();

})

.ConfigureServices((hostContext, services) =>

{

services.AddOptions();

services.Configure<Application.Configuration.Configuration>(hostContext.Configuration.GetSection("Section in AppSettings"));

NLog.Logger logger = NLog.LogManager.GetLogger("NLog Name");

services.AddSingleton(logger);

services.Configure((Localization.Configuration.LocalizationConfiguration options) => hostContext.Configuration.GetSection("Localization Section in AppSettings").Bind(options));

services.AddSingleton<Localization.ILocalizationService, Localization.LocalizationService>();

services.AddSingleton<IMyClass, MyClass>();

});

return host.Start();

}

public T GetService<T>() => (T)Host.Services.GetService(typeof(T));

}

Die eigentliche Test Klasse erbt nun von diesen BaseUnitTest. Nun kann ein Propertiy erzeugt werden, welche einen Service aus der Dependency Injection ausliest:

public MyClass MyClass => base.GetService<MyClass>();

1

public MyClass MyClass => base.GetService<MyClass>();

Posted on 10. Juli 2020 by Andreas in Allgemein, C#

SQL CPU Last und Gesamtdauer von Query testen

set statistics time on
 
select 1


set statistics time off

set statistics time on

select 1

set statistics time off

Posted on 26. Mai 2020 by Andreas in SQL

.gitignore SSIS dtsx Dateien hinzufügen

in der VisualStudio .gitignore: https://www.gitignore.io/api/visualstudio

wird das komplette Verzeichnis “obj” exkludiert. Die packages (.dtsx) aus SSIS befindet sich aber gerade dort.

Daher muss man folgende Zeile auskommentieren:

#[Oo]bj/

#[Oo]bj/

und unter diesen Block einen neuen Block hinzufügen:

#SSIS
!**/[Oo]bj/**/*.*
**/[Oo]bj/**/*.*
!**/[Oo]bj/**/*.dtsx
!**/[Oo]bj/**/*.conmgr

#SSIS

!**/[Oo]bj/**/*.*

**/[Oo]bj/**/*.*

!**/[Oo]bj/**/*.dtsx

!**/[Oo]bj/**/*.conmgr

meine komplette .gitignore sieht demnach so aus:

## 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

# User-specific files
*.rsuser
*.suo
*.user
*.userosscache
*.sln.docstates

# User-specific files (MonoDevelop/Xamarin Studio)
*.userprefs

# Mono auto generated files
mono_crash.*

# Build results
[Dd]ebug/
[Dd]ebugPublic/
[Rr]elease/
[Rr]eleases/
x64/
x86/
[Ww][Ii][Nn]32/
[Aa][Rr][Mm]/
[Aa][Rr][Mm]64/
bld/
[Bb]in/
#[Oo]bj/
[Ll]og/
[Ll]ogs/

#SSIS
!**/[Oo]bj/**/*.*
**/[Oo]bj/**/*.*
!**/[Oo]bj/**/*.dtsx
!**/[Oo]bj/**/*.conmgr

# Visual Studio 2015/2017 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.*

# NUnit
*.VisualState.xml
TestResult.xml
nunit-*.xml

# Build Results of an ATL Project
[Dd]ebugPS/
[Rr]eleasePS/
dlldata.c

# Benchmark Results
BenchmarkDotNet.Artifacts/

# .NET Core
project.lock.json
project.fragment.lock.json
artifacts/

# ASP.NET Scaffolding
ScaffoldingReadMe.txt

# StyleCop
StyleCopReport.xml

# Files built by Visual Studio
*_i.c
*_p.c
*_h.h
*.ilk
*.meta
*.obj
*.iobj
*.pch
*.pdb
*.ipdb
*.pgc
*.pgd
*.rsp
*.sbr
*.tlb
*.tli
*.tlh
*.tmp
*.tmp_proj
*_wpftmp.csproj
*.log
*.vspscc
*.vssscc
.builds
*.pidb
*.svclog
*.scc

# Chutzpah Test files
_Chutzpah*

# Visual C++ cache files
ipch/
*.aps
*.ncb
*.opendb
*.opensdf
*.sdf
*.cachefile
*.VC.db
*.VC.VC.opendb

# Visual Studio profiler
*.psess
*.vsp
*.vspx
*.sap

# Visual Studio Trace Files
*.e2e

# TFS 2012 Local Workspace
$tf/

# Guidance Automation Toolkit
*.gpState

# ReSharper is a .NET coding add-in
_ReSharper*/
*.[Rr]e[Ss]harper
*.DotSettings.user

# TeamCity is a build add-in
_TeamCity*

# DotCover is a Code Coverage Tool
*.dotCover

# AxoCover is a Code Coverage Tool
.axoCover/*
!.axoCover/settings.json

# Coverlet is a free, cross platform Code Coverage Tool
coverage*[.json, .xml, .info]

# Visual Studio code coverage results
*.coverage
*.coveragexml

# NCrunch
_NCrunch_*
.*crunch*.local.xml
nCrunchTemp_*

# MightyMoose
*.mm.*
AutoTest.Net/

# Web workbench (sass)
.sass-cache/

# Installshield output folder
[Ee]xpress/

# DocProject is a documentation generator add-in
DocProject/buildhelp/
DocProject/Help/*.HxT
DocProject/Help/*.HxC
DocProject/Help/*.hhc
DocProject/Help/*.hhk
DocProject/Help/*.hhp
DocProject/Help/Html2
DocProject/Help/html

# Click-Once directory
publish/

# Publish Web Output
*.[Pp]ublish.xml
*.azurePubxml
# Note: 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

# Microsoft Azure Web App publish settings. Comment the next line if you want to
# checkin your Azure Web App publish settings, but sensitive information contained
# in these scripts will be unencrypted
PublishScripts/

# NuGet Packages
*.nupkg
# NuGet Symbol Packages
*.snupkg
# The packages folder can be ignored because of Package Restore
**/[Pp]ackages/*
# except build/, which is used as an MSBuild target.
!**/[Pp]ackages/build/
# Uncomment if necessary however generally it will be regenerated when needed
#!**/[Pp]ackages/repositories.config
# NuGet v3's project.json files produces more ignorable files
*.nuget.props
*.nuget.targets

# Microsoft Azure Build Output
csx/
*.build.csdef

# Microsoft Azure Emulator
ecf/
rcf/

# Windows Store app package directories and files
AppPackages/
BundleArtifacts/
Package.StoreAssociation.xml
_pkginfo.txt
*.appx
*.appxbundle
*.appxupload

# Visual Studio cache files
# files ending in .cache can be ignored
*.[Cc]ache
# but keep track of directories ending in .cache
!?*.[Cc]ache/

# Others
ClientBin/
~$*
*~
*.dbmdl
*.dbproj.schemaview
*.jfm
*.pfx
*.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/

# RIA/Silverlight projects
Generated_Code/

# Backup & report files from converting an old project file
# to a newer Visual Studio version. Backup files are not needed,
# because we have git ;-)
_UpgradeReport_Files/
Backup*/
UpgradeLog*.XML
UpgradeLog*.htm
ServiceFabricBackup/
*.rptproj.bak

# SQL Server files
*.mdf
*.ldf
*.ndf

# Business Intelligence projects
*.rdl.data
*.bim.layout
*.bim_*.settings
*.rptproj.rsuser
*- [Bb]ackup.rdl
*- [Bb]ackup ([0-9]).rdl
*- [Bb]ackup ([0-9][0-9]).rdl

# Microsoft Fakes
FakesAssemblies/

# GhostDoc plugin setting file
*.GhostDoc.xml

# Node.js Tools for Visual Studio
.ntvs_analysis.dat
node_modules/

# Visual Studio 6 build log
*.plg

# Visual Studio 6 workspace options file
*.opt

# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)
*.vbw

# Visual Studio LightSwitch build output
**/*.HTMLClient/GeneratedArtifacts
**/*.DesktopClient/GeneratedArtifacts
**/*.DesktopClient/ModelManifest.xml
**/*.Server/GeneratedArtifacts
**/*.Server/ModelManifest.xml
_Pvt_Extensions

# Paket dependency manager
.paket/paket.exe
paket-files/

# FAKE - F# Make
.fake/

# CodeRush personal settings
.cr/personal

# Python Tools for Visual Studio (PTVS)
__pycache__/
*.pyc

# Cake - Uncomment if you are using it
# tools/**
# !tools/packages.config

# Tabs Studio
*.tss

# Telerik's JustMock configuration file
*.jmconfig

# BizTalk build output
*.btp.cs
*.btm.cs
*.odx.cs
*.xsd.cs

# OpenCover UI analysis results
OpenCover/

# Azure Stream Analytics local run output
ASALocalRun/

# MSBuild Binary and Structured Log
*.binlog

# NVidia Nsight GPU debugger configuration file
*.nvuser

# MFractors (Xamarin productivity tool) working folder
.mfractor/

# Local History for Visual Studio
.localhistory/

# BeatPulse healthcheck temp database
healthchecksdb

# Backup folder for Package Reference Convert tool in Visual Studio 2017
MigrationBackup/

# Ionide (cross platform F# VS Code tools) working folder
.ionide/

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

## 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

# User-specific files

*.rsuser

*.suo

*.user

*.userosscache

*.sln.docstates

# User-specific files (MonoDevelop/Xamarin Studio)

*.userprefs

# Mono auto generated files

mono_crash.*

# Build results

[Dd]ebug/

[Dd]ebugPublic/

[Rr]elease/

[Rr]eleases/

x64/

x86/

[Ww][Ii][Nn]32/

[Aa][Rr][Mm]/

[Aa][Rr][Mm]64/

bld/

[Bb]in/

#[Oo]bj/

[Ll]og/

[Ll]ogs/

#SSIS

!**/[Oo]bj/**/*.*

**/[Oo]bj/**/*.*

!**/[Oo]bj/**/*.dtsx

!**/[Oo]bj/**/*.conmgr

# Visual Studio 2015/2017 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.*

# NUnit

*.VisualState.xml

TestResult.xml

nunit-*.xml

# Build Results of an ATL Project

[Dd]ebugPS/

[Rr]eleasePS/

dlldata.c

# Benchmark Results

BenchmarkDotNet.Artifacts/

# .NET Core

project.lock.json

project.fragment.lock.json

artifacts/

# ASP.NET Scaffolding

ScaffoldingReadMe.txt

# StyleCop

StyleCopReport.xml

# Files built by Visual Studio

*_i.c

*_p.c

*_h.h

*.ilk

*.meta

*.obj

*.iobj

*.pch

*.pdb

*.ipdb

*.pgc

*.pgd

*.rsp

*.sbr

*.tlb

*.tli

*.tlh

*.tmp

*.tmp_proj

*_wpftmp.csproj

*.log

*.vspscc

*.vssscc

.builds

*.pidb

*.svclog

*.scc

# Chutzpah Test files

_Chutzpah*

# Visual C++ cache files

ipch/

*.aps

*.ncb

*.opendb

*.opensdf

*.sdf

*.cachefile

*.VC.db

*.VC.VC.opendb

# Visual Studio profiler

*.psess

*.vsp

*.vspx

*.sap

# Visual Studio Trace Files

*.e2e

# TFS 2012 Local Workspace

$tf/

# Guidance Automation Toolkit

*.gpState

# ReSharper is a .NET coding add-in

_ReSharper*/

*.[Rr]e[Ss]harper

*.DotSettings.user

# TeamCity is a build add-in

_TeamCity*

# DotCover is a Code Coverage Tool

*.dotCover

# AxoCover is a Code Coverage Tool

.axoCover/*

!.axoCover/settings.json

# Coverlet is a free, cross platform Code Coverage Tool

coverage*[.json, .xml, .info]

# Visual Studio code coverage results

*.coverage

*.coveragexml

# NCrunch

_NCrunch_*

.*crunch*.local.xml

nCrunchTemp_*

# MightyMoose

*.mm.*

AutoTest.Net/

# Web workbench (sass)

.sass-cache/

# Installshield output folder

[Ee]xpress/

# DocProject is a documentation generator add-in

DocProject/buildhelp/

DocProject/Help/*.HxT

DocProject/Help/*.HxC

DocProject/Help/*.hhc

DocProject/Help/*.hhk

DocProject/Help/*.hhp

DocProject/Help/Html2

DocProject/Help/html

# Click-Once directory

publish/

# Publish Web Output

*.[Pp]ublish.xml

*.azurePubxml

# Note: 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

# Microsoft Azure Web App publish settings. Comment the next line if you want to

# checkin your Azure Web App publish settings, but sensitive information contained

# in these scripts will be unencrypted

PublishScripts/

# NuGet Packages

*.nupkg

# NuGet Symbol Packages

*.snupkg

# The packages folder can be ignored because of Package Restore

**/[Pp]ackages/*

# except build/, which is used as an MSBuild target.

!**/[Pp]ackages/build/

# Uncomment if necessary however generally it will be regenerated when needed

#!**/[Pp]ackages/repositories.config

# NuGet v3's project.json files produces more ignorable files

*.nuget.props

*.nuget.targets

# Microsoft Azure Build Output

csx/

*.build.csdef

# Microsoft Azure Emulator

ecf/

rcf/

# Windows Store app package directories and files

AppPackages/

BundleArtifacts/

Package.StoreAssociation.xml

_pkginfo.txt

*.appx

*.appxbundle

*.appxupload

# Visual Studio cache files

# files ending in .cache can be ignored

*.[Cc]ache

# but keep track of directories ending in .cache

!?*.[Cc]ache/

# Others

ClientBin/

~$*

*.dbmdl

*.dbproj.schemaview

*.jfm

*.pfx

*.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/

# RIA/Silverlight projects

Generated_Code/

# Backup & report files from converting an old project file

# to a newer Visual Studio version. Backup files are not needed,

# because we have git ;-)

_UpgradeReport_Files/

Backup*/

UpgradeLog*.XML

UpgradeLog*.htm

ServiceFabricBackup/

*.rptproj.bak

# SQL Server files

*.mdf

*.ldf

*.ndf

# Business Intelligence projects

*.rdl.data

*.bim.layout

*.bim_*.settings

*.rptproj.rsuser

*- [Bb]ackup.rdl

*- [Bb]ackup ([0-9]).rdl

*- [Bb]ackup ([0-9][0-9]).rdl

# Microsoft Fakes

FakesAssemblies/

# GhostDoc plugin setting file

*.GhostDoc.xml

# Node.js Tools for Visual Studio

.ntvs_analysis.dat

node_modules/

# Visual Studio 6 build log

*.plg

# Visual Studio 6 workspace options file

*.opt

# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)

*.vbw

# Visual Studio LightSwitch build output

**/*.HTMLClient/GeneratedArtifacts

**/*.DesktopClient/GeneratedArtifacts

**/*.DesktopClient/ModelManifest.xml

**/*.Server/GeneratedArtifacts

**/*.Server/ModelManifest.xml

_Pvt_Extensions

# Paket dependency manager

.paket/paket.exe

paket-files/

# FAKE - F# Make

.fake/

# CodeRush personal settings

.cr/personal

# Python Tools for Visual Studio (PTVS)

__pycache__/

*.pyc

# Cake - Uncomment if you are using it

# tools/**

# !tools/packages.config

# Tabs Studio

*.tss

# Telerik's JustMock configuration file

*.jmconfig

# BizTalk build output

*.btp.cs

*.btm.cs

*.odx.cs

*.xsd.cs

# OpenCover UI analysis results

OpenCover/

# Azure Stream Analytics local run output

ASALocalRun/

# MSBuild Binary and Structured Log

*.binlog

# NVidia Nsight GPU debugger configuration file

*.nvuser

# MFractors (Xamarin productivity tool) working folder

.mfractor/

# Local History for Visual Studio

.localhistory/

# BeatPulse healthcheck temp database

healthchecksdb

# Backup folder for Package Reference Convert tool in Visual Studio 2017

MigrationBackup/

# Ionide (cross platform F# VS Code tools) working folder

.ionide/

Posted on 30. März 2020 by Andreas in Allgemein

Step 1: Gitea installieren

Chocolaty ist eine Windows Umgebung um Anwendungen über Kommandozeile zu installieren:
1. https://chocolatey.org/install
GO installieren
1. https://golang.org/dl/
cmd öffnen und echo %GOPATH% eingeben. Wenn als Ergebnis wieder %GOPATH% steht, Windows neustarten und nochmal prüfen. Andernfalls unter Systemsteurung -> System -> Erweitert -> Umgebungsvariablen die GOPATH Variable setzen
cmd als Admin starten und folgende Befehle eingeben:

#Git installieren bei Abfrage mit A und Enter bestätigen
choco install git

#NodeJs installieren 
choco install nodejs 

#Make installieren 
choco install make

#Cmd Neustarten um Umgebungsvariablen zu laden
refreshenv

#Neuste Version updaten
git clone https://github.com/git/git

#Go Verzeichnis erstellen
mkdir %GOPATH%

#Zu Go Verzeichnis navigieren
cd %GOPATH%

#Gitea herunterladen
go get -d -u code.gitea.io/gitea

#Gitea Verzeichnis navigieren
cd "%GOPATH%/src/code.gitea.io/gitea"

#Gitea builden
go build

#Gitea Verzeichnis zu c:\gitea kopieren
xcopy "%GOPATH%/src/code.gitea.io/gitea" "C:\gitea\" /s/h/e/k/f/c

#app.ini kopieren mit F und Enter File bestätigen
xcopy "C:\gitea\custom\conf\app.ini.sample" "C:\gitea\custom\conf\app.ini"

#Computernamen ausgeben
echo %COMPUTERNAME%

#Zeile 11 in der app.ini bearbeiten ($ am Ende nicht vergessen): RUN_USER = MEIN_COMPUTERNAME$

#Git installieren bei Abfrage mit A und Enter bestätigen

choco install git

#NodeJs installieren

choco install nodejs

#Make installieren

choco install make

#Cmd Neustarten um Umgebungsvariablen zu laden

refreshenv

#Neuste Version updaten

git clone https://github.com/git/git

#Go Verzeichnis erstellen

mkdir %GOPATH%

#Zu Go Verzeichnis navigieren

cd %GOPATH%

#Gitea herunterladen

go get -d -u code.gitea.io/gitea

#Gitea Verzeichnis navigieren

cd "%GOPATH%/src/code.gitea.io/gitea"

#Gitea builden

go build

#Gitea Verzeichnis zu c:\gitea kopieren

xcopy "%GOPATH%/src/code.gitea.io/gitea" "C:\gitea\" /s/h/e/k/f/c

#app.ini kopieren mit F und Enter File bestätigen

xcopy "C:\gitea\custom\conf\app.ini.sample" "C:\gitea\custom\conf\app.ini"

#Computernamen ausgeben

echo %COMPUTERNAME%

#Zeile 11 in der app.ini bearbeiten ($ am Ende nicht vergessen): RUN_USER = MEIN_COMPUTERNAME$

Nun ist der Service unter http://localhost:3000 erreichbar, zeigt aber Fehler an. Daher muss man das Package herunterladen:
1. https://dl.gitea.io/gitea/1.11.0/gitea-1.11.0-windows-4.0-amd64.exe
2. Diese direkt in das Verzeichnis c:\gitea kopieren

#Service installieren und starten
sc create gitea_1_11_0 start= auto binPath= ""C:\gitea\gitea-1.11.0-windows-4.0-amd64.exe" web --config "C:\gitea\custom\conf\app.ini""

#Service starten, falls nicht bereits gestartet  (stop stoppt ihn wieder) 
net start gitea

#Service installieren und starten

sc create gitea_1_11_0 start= auto binPath= ""C:\gitea\gitea-1.11.0-windows-4.0-amd64.exe" web --config "C:\gitea\custom\conf\app.ini""

#Service starten, falls nicht bereits gestartet (stop stoppt ihn wieder)

net start gitea

MS SQL Server vorbereiten

Im SQL Management Studio nun eine Neue Datenbank mit dem Namen “Gitea” erstellen
Unter Security -> Logins einen Neuen SQL User “gitea-user” erstellen.
R. Maustaste auf den User -> Properties -> Server Roles und nur die neue Gitea Datenbank zuweisen
Mindestens einmal als dieser User einlogen und das neue Passwort setzen
Wieder mit Properties -> Global die Haken bei Enforce Password expiration raus nehmen

SSH Server einrichten

PowerShell als Admin öffnen

## Install  OpenSSH.Server 
Add-WindowsCapability -Online -Name OpenSSH.Server

## Install  OpenSSH.Client
Add-WindowsCapability -Online -Name OpenSSH.Client

## Change server start-up to Automatic 
Set-Service -Name sshd -StartupType ‘Automatic’ 

## Start the Server and change start-up to Automatic
Start-Service sshd

## Change server start-up to Automatic 
Set-Service -Name ssh-agent -StartupType ‘Automatic’ 

## Start the Server and change start-up to Automatic 
Start-Service ssh-agent

## Install OpenSSH.Server

Add-WindowsCapability -Online -Name OpenSSH.Server

## Install OpenSSH.Client

Add-WindowsCapability -Online -Name OpenSSH.Client

## Change server start-up to Automatic

Set-Service -Name sshd -StartupType ‘Automatic’

## Start the Server and change start-up to Automatic

Start-Service sshd

## Change server start-up to Automatic

Set-Service -Name ssh-agent -StartupType ‘Automatic’

## Start the Server and change start-up to Automatic

Start-Service ssh-agent

Zum SSH Test einloggen eingeben. Standard Port ist 22 und sollte in der Firewall freigeschaltet sein

ssh [Windows User]@Hostname bzw. Ip Adresse Danach das Passwort

1
2

ssh [Windows User]@Hostname bzw. Ip Adresse
Danach das Passwort

Posted on 12. Februar 2020 by Andreas in Allgemein

Microservices mit .Net Framework und Core ohne Docker

Momentan liest man überall von Microservices und welche Vorteile diese Architektur mit sich bringt. Zwar wird immer wieder aufgeführt, dass Microservices Polyglot (Eine Architektur mit unterschiedlichen Programmiersprachen) unterstützen können. Tatsächlich findet man aber nur Anleitungen (In der Microsoft Welt) Zu .Net Core, in Verbindung mit Docker und Azure.

Mein Ziel ist es eine Architektur ohne Docker (Da auf VMs nicht unterstützt wird) und eine Verbindung aus Core und .Net Framework herzustellen. Aus einer Reihe von nachhaltigen Frameworks soll die Entwicklung in CD (Continues Delivery) gestaltet werden. TFS und GitLab scheiden wegen ihren Lizenzmodell aus.

CodeRepository: Git -> https://git-scm.com/download/win
Build Server: Jenkins -> https://jenkins.io/download/
- https://www.guru99.com/jenkin-continuous-integration.html
Api Gateway (Kommunikation ClientApi zu Microservices) Ocelot : https://github.com/ThreeMammals/Ocelot
Kommunikationsprotokoll zwischen Microservices: gRPC (Da schneller als Http)
Sicherheit unter Microservices: JWT Token
Authentifizierung Microservice mit OAuth 2.0 und OWIN Middleware: https://oauth.net/code/dotnet/
Repository: Implementierung mit Dapper: https://github.com/StackExchange/Dapper
Repository Cache: https://github.com/MichaCo/CacheManager
Datenbank Code Migration SSDT: SQL Server Data Tools
- https://www.youtube.com/watch?v=6ass_PYECmM&t
- https://arapaima.uk/post/2017-04-04-jenkins-windows-git-ssdt-profit/
(Optional) Search Engine: https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/introduction.html
- https://www.red-gate.com/simple-talk/dotnet/net-development/how-to-build-a-search-page-with-elasticsearch-and-net/

Posted on 10. Februar 2020 by Andreas in Allgemein

Windows Bug Tooltip bleibt hängen

Wahrscheinlich jeder kennt es, wenn plötzlich irgendwo im Bildschirm ein Tooltip hängt und nicht weg geht.

Dann kann man einfach Windows+D 2x drücken und dann ist der weg

Posted on 18. Januar 2020 by Andreas in Allgemein

SQL Rekursion Parent zu Child / Child zu Parent

Erster Block im CTE: In der WHERE Bedingung wird die Child-Id übergeben

Zweiter Block: Join auf die CTE, ParentId mit der TabelleId

DECLARE @IterationId INT = 4;


-- Rekursion Child to Parent
;WITH CTE AS (
   SELECT t1.IterationId
		  , t1.ParentId	  		  

		  , 0 AS [Level]	
    FROM Messenger.tblIteration t1 	
	WHERE t1.IterationId = @IterationId	

   UNION ALL
   SELECT 
			t1.IterationId
		  , t1.ParentId	  		  		  
		  
		  , CTE.[Level] + 1 AS [Level]	

	FROM Messenger.tblIteration t1 
	INNER JOIN CTE ON CTE.ParentId = t1.IterationId 
)

SELECT 
*
FROM CTE
ORDER BY Level

DECLARE @IterationId INT = 4;

-- Rekursion Child to Parent

;WITH CTE AS (

SELECT t1.IterationId

, t1.ParentId

, 0 AS [Level]

FROM Messenger.tblIteration t1

WHERE t1.IterationId = @IterationId

UNION ALL

SELECT

t1.IterationId

, t1.ParentId

, CTE.[Level] + 1 AS [Level]

FROM Messenger.tblIteration t1

INNER JOIN CTE ON CTE.ParentId = t1.IterationId

)

SELECT

FROM CTE

ORDER BY Level

Erster Block im CTE: In der WHERE Bedingung wird die ParentId mit NULL angegeben

Zweiter Block: Join auf die CTE, Id mit der Tabelle ParentId

---- Rekursion Parent to Child
;WITH CTE AS (
   SELECT t1.IterationId
		  , t1.ParentId	  		  

		  , 0 AS [Level]	
    FROM Messenger.tblIteration t1 	
	WHERE t1.ParentId IS NULL

   UNION ALL
   SELECT 
			t1.IterationId
		  , t1.ParentId	  		  		  
		  
		  , CTE.[Level] + 1 AS [Level]	

	FROM Messenger.tblIteration t1 
	INNER JOIN CTE ON CTE.IterationId = t1.ParentId 
)

SELECT 
*
FROM CTE
ORDER BY Level

---- Rekursion Parent to Child

;WITH CTE AS (

SELECT t1.IterationId

, t1.ParentId

, 0 AS [Level]

FROM Messenger.tblIteration t1

WHERE t1.ParentId IS NULL

UNION ALL

SELECT

t1.IterationId

, t1.ParentId

, CTE.[Level] + 1 AS [Level]

FROM Messenger.tblIteration t1

INNER JOIN CTE ON CTE.IterationId = t1.ParentId

)

SELECT

FROM CTE

ORDER BY Level

Posted on 6. Januar 2020 by Andreas in SQL

Visual Studio Build Events

Wenn man nach einem Build eine Applikation starten möchte, muss man einen Umweg um eine bat Datei gehen.

R. Maustaste auf das Projekt in Visual Studio, dann auf “Build” und unter Pre oder Post folgendes eingeben

call meinPfadZurBatDatei\startPublisher.bat

und unter diesen Pfad müssen wir eine bat Datei erstellen, die wiederum eine exe ausführt

einfach start meinPfadZurExe.exe in die bat Datei schreiben

Posted on 23. Dezember 2019 by Andreas in Allgemein, CrossLoom

HTML / CSS Container erstellen, der die Zeilen formatiert wie der Inhalt des Containers

einfach <pre> nutzen

Siehe https://www.mediaevent.de/xhtml/pre.html

Posted on 10. Dezember 2019 by Andreas in CSS, HTML

SQL Server Remote Zugriff

Um auf eine SQL Instanz per Remote (von außen) zugreifen zu können, muss man in der Firewall folgende Ports aufmachen:

InBound (Eingehende): TCP 1433 (für z.B. SSMS), UDP 1434 (für ODBC Verbindungen)

OutBound (Ausgehende): TCP 1433

Zusätzlich die Dynamic aus “SQL Server Network Configuration” -> “Protocols for [INSTANZ]” -> “TCP/IP” -> Reiter “IPAdresses” -> Im Feld “IPAll” -> TCP Dynamic Ports

Auserdem muss der TCP/IP Client Protokoll in SQL Configuration eingeschaltet werden:

außerdem muss der SQL Browser Service laufen:

Posted on 1. Dezember 2019 by Andreas in Allgemein, SQL

Tags: Remote, SQL, von außen

Right Hand of the Head of Development

Integrations Test mit Dependency Injection MsTest v2 .Net Core 3.1

SQL CPU Last und Gesamtdauer von Query testen

.gitignore SSIS dtsx Dateien hinzufügen

Step 1: Gitea installieren

MS SQL Server vorbereiten

SSH Server einrichten

Microservices mit .Net Framework und Core ohne Docker

Windows Bug Tooltip bleibt hängen

SQL Rekursion Parent zu Child / Child zu Parent

Visual Studio Build Events

HTML / CSS Container erstellen, der die Zeilen formatiert wie der Inhalt des Containers

SQL Server Remote Zugriff

Seiten

Neueste Beiträge

Neueste Kommentare

Archive

Right Hand of the Head of Development

MS SQL Server vorbereiten

SSH Server einrichten

Search this site

Seiten

Neueste Beiträge

Neueste Kommentare

Archive