We Keep Coding

How to pass parameter as class not as string to New-Object?

I can't seem to pass $outputStream as Stream to StreamWritter constructor. It gets passed as string and then it invokes wrong constructor that expects string not stream.
$tcpClient = New-Object System.Net.Sockets.TCPClient
$connect = $tcpClient.BeginConnect("localhost", 8080, $null, $null)
$success = $connect.AsyncWaitHandle.WaitOne($testTimeoutMs, $true)
[System.Net.Sockets.NetworkStream]$outputStream = $tcpClient.GetStream()
$writer = New-Object System.IO.StreamWriter -ArgumentList $outputStream, [System.Text.Encoding].ASCII
I want to invnoke this (https://msdn.microsoft.com/en-us/library/3aadshsx(v=vs.110).aspx) constructor but it invokes one with string parameters instead of Stream.
This results in this error:
New-Object : Exception calling ".ctor" with "2" argument(s): "The process cannot access the file 'C:\Users\Maciej\System.Net.Sockets.NetworkStream' because it is being used by anothe
r process."
At line:1 char:12
+ $writer = New-Object System.IO.StreamWriter -ArgumentList $outputStr ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvocationException
+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand
How to force to pass this parameter as Stream not as string?

Your problem is trying to access the [Encoding] class's static member with the wrong syntax:
[Text.Encoding].ASCII
In PowerShell, you access type static members with the following syntax:
[Text.Encoding]::ASCII
This object has the type [System.Text.ASCIIEncoding] according to .GetType() which inherits from [System.Text.Encoding] and should resolve the constructor errors you're receiving:
$tcpClient = New-Object -TypeName 'System.Net.Sockets.TCPClient'
$connect = $tcpClient.BeginConnect('localhost', 8080, $Null, $Null)
$success = $connect.AsyncWaitHandle.WaitOne($testTimeoutMs, $True)
$outputStream = $tcpClient.GetStream()
$writer = New-Object -TypeName 'System.IO.StreamWriter' -ArgumentList #($outputStream, [System.Text.Encoding]::ASCII)
As a side-note, in v5+, you can natively call the constructor method:
$streamWriter = [IO.StreamWriter]::new($outputStream, [Text.Encoding]::ASCII)

What is the best way to change the solution name programmatically in asp.net core?

I'm looking for a way to provide a changing solution/project name functionality to ASP.NET Core Projects. My first idea is to do it programmatically in an installer feature where the developer would write the project name. Is it possible in .NET Framework or via Powershell?
Thanks!

You can use the below function which will help you in changing:
Here are the reference links:
1) Link 1
2) Link 2
function Rename-Project
{
# designed to run from the src folder
param(
[string]$projectName=$(throw "projectName required."),
[string]$newProjectName=$(throw "newProjectName required.")
)
if(!(Test-Path $projectName)){
Write-Error "No project folder '$projectName' found"
return
}
if(!(Test-Path $projectName\$projectName.csproj)){
Write-Error "No project '$projectName\$projectName.dll' found"
return
}
if((Test-Path $newProjectName)){
Write-Error "Project '$newProjectName' already exists"
return
}
# project
hg rename $projectName\$projectName.csproj $projectName\$newProjectName.csproj
# folder
hg rename $projectName $newProjectName
# assembly title
$assemblyInfoPath = "$newProjectName\Properties\AssemblyInfo.cs"
(gc $assemblyInfoPath) -replace """$projectName""","""$newProjectName""" | sc $assemblyInfoPath
# root namespace
$projectFile = "$newProjectName\$newProjectName.csproj"
(gc $projectFile) -replace "<RootNamespace>$projectName</RootNamespace>","<RootNamespace>$newProjectName</RootNamespace>" | sc $projectFile
# assembly name
(gc $projectFile) -replace "<AssemblyName>$projectName</AssemblyName>","<AssemblyName>$newProjectName</AssemblyName>" | sc $projectFile
# other project references
gci -Recurse -Include *.csproj |% { (gc $_) -replace "..\\$projectName\\$projectName.csproj", "..\$newProjectName\$newProjectName.csproj" | sc $_ }
gci -Recurse -Include *.csproj |% { (gc $_) -replace "<Name>$projectName</Name>", "<Name>$newProjectName</Name>" | sc $_ }
# solution
gci -Recurse -Include *.sln |% { (gc $_) -replace "\""$projectName\""", """$newProjectName""" | sc $_ }
gci -Recurse -Include *.sln |% { (gc $_) -replace "\""$projectName\\$projectName.csproj\""", """$newProjectName\$newProjectName.csproj""" | sc $_ }
}

How do I get SonarQube to ignore the GlobalSuppressions.cs file?

I want to exclude the GlobalSuppressions.cs file from SonarQube analysis so that it doesn't look at the System.Diagnostics.CodeAnalysis.SuppressMessage directives in there.
These are in the root of each project, but not in the root where the solution is: E.g.
I set this in the admin:
Namely, **/GlobalSuppressions.cs.
There are many projects in each solution, so I would like to avoid referencing each individually if possible.

My solution to this problem was to use a Powershell script to clear the globalsupressions.cs file and alter the ruleset from one that errored (CodeAnalysisRulesErrors.ruleset or CodeAnalysisRulesUnitTestsErrors.ruleset) to one that threw warnings (CodeAnalysisRules.ruleset or CodeAnalysisRulesUnitTests.ruleset), that way SonarQube correctly reported on the technical debt.
[CmdletBinding()]
param (
[string]$localWorkspace
)
begin{}
process
{
try
{
$localWorkspace = "$($env:SYSTEM_DEFAULTWORKINGDIRECTORY)\$($localWorkspace)"
$localWorkspace = $localWorkspace -replace "/" , "\"
$localWorkspace = $localWorkspace -replace "\\" , "\"
Write-Verbose $localWorkspace
#Work out top level directories, excluding system dirs
[System.Collections.ArrayList]$topLevelDirs = #()
$topLevelItem = Get-ChildItem $localWorkspace -Exclude #("node_modules", "packages", "Common", ".nuget", ".vs", "_Resharper.Caches", "Javascript")
foreach ($item in $topLevelItem)
{
if (Test-Path $item -PathType Container) {
Write-Verbose $item
$topLevelDirs.Add($item)
}
}
foreach ($topLevelFolder in $topLevelDirs)
{
Write-Verbose $topLevelFolder
$ServiceDirs = Get-ChildItem -Path $topLevelFolder -Filter GlobalSuppressions.cs -Recurse
foreach ($sd in $ServiceDirs)
{
Write-Verbose $sd
Clear-Content $sd.FullName
}
Get-ChildItem -Path $topLevelFolder -Filter *.csproj -Recurse | ForEach {
Write-Verbose $_.FullName
(Get-Content $_.FullName | ForEach { $_ -replace 'CodeAnalysisRulesErrors.ruleset', 'CodeAnalysisRules.ruleset' }) | Set-Content $_.FullName
(Get-Content $_.FullName | ForEach { $_ -replace 'CodeAnalysisRulesUnitTestsErrors.ruleset', 'CodeAnalysisRulesUnitTests.ruleset' }) | Set-Content $_.FullName
}
}
}
catch
{
write-host "Caught an exception:"
write-host "Exception Type: $($_.Exception.GetType().FullName)"
write-host "Exception Message: $($_.Exception.Message)"
}
}
end{}

Call class file method from NuGet package using Powershell

I'm trying to create a nuget package from my class libary. So far I managed to create and install the package in a test project, but I also want to create a package manager command. My NuGet package is created with the NuGet Package Explorer.
NuGet Package structure
NuGet files content
init.ps1
param($installPath, $toolsPath, $package)
Import-Module (Join-Path $toolsPath MyNuGetCommands.psm1)
MyNuGetCommands.psm1
function Hello($name, $city)
{
Write-Host (‘Hello ‘ + $name + ‘. See you soon in ‘ + $city + ‘.’)
$lib = [Reflection.Assembly]::LoadFile("\\lib\EF.XML.dll")
$obj = new-object Parser
$result = $obj.UpdateXml()
}
Export-ModuleMember Hello
Register-TabExpansion ‘Hello’ #{
‘name’ = { "MSFTees", "MVPs", "My friends" };
‘city’ = { "Redmond", "Seattle", "Bellevue", "Duvall" };
}
I found the Hello function on the net and it worked in my project so I thougt lets add some lines found here to call my C# method. When I call the Hello function in my test project I get this errors:
Error 1
Exception calling "LoadFile" with "1" argument(s): "Cannot find the network path. (Exception from HRESULT: 0x80070035)" At
\svr\redirectedfolders\Stage\my documents\visual studio
2015\Projects\Test\packages\XML.EF.1.0.0\tools\MyNuGetCommands.psm1:5
char:43
+ $lib = [Reflection.Assembly]::LoadFile <<<< ("\lib\EF.XML.dll")
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
Error 2
New-Object : Cannot find type [Parser]: make sure the assembly
containing this type is loaded. At
\svr\redirectedfolders\Stage\my documents\visual studio
2015\Projects\Test\packages\XML.EF.1.0.0\tools\MyNuGetCommands.psm1:6
char:22
+ $obj = new-object <<<< Parser
+ CategoryInfo : InvalidType: (:) [New-Object], PSArgumentException
+ FullyQualifiedErrorId : TypeNotFound,Microsoft.PowerShell.Commands.NewObjectCommand
Error 3
You cannot call a method on a null-valued expression. At
\svr\redirectedfolders\Stage\my documents\visual studio
2015\Projects\Test\packages\XML.EF.1.0.0\tools\MyNuGetCommands.psm1:7
char:29
+ $result = $obj.UpdateXml <<<< ()
+ CategoryInfo : InvalidOperation: (UpdateXml:String) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull
So I think in the above errors obj is null but how can I fix this (I am not sure if LoadFile path is correct)? I did run set-executionpolicy RemoteSigned in Powershell.
Parser.cs file structure in EF.XML.dll
public class Parser
{
public void UpdateXml()
{
//code
}
}
This is the code to I use to call the method from a .cs file (which works but I want to call this from my Powershell Module:
var parser = new EF.XML.Parser();
parser.UpdateXml();

Using PowerShell in nuget package to edit Global.asax

Using a Install.ps1 script with a Nuget Package, I'm attempting to add code to the Global.asax.cs file for customization purposes. With my Install.ps1 script the -replace command is not working. Infact I'm not able to assign any text to the variable $a I'm using with -replace and have it written to the "Global.asax.cs" file. The 3 lines of script involving -replace and the clipboard do work with "Windows PowerShell" outside of nuget. I know that the variable $a is passing along content from the clipboard since commenting out "#$customGlobalAsax.Document.Selection.Copy()" will write whatever happens to be in the clipboard into the Global.asax.cs file.
Any Suggestions? Thanks.
param($installPath, $toolsPath, $package, $project)
$customGlobalAsax = $project.ProjectItems | ForEach-Object { $_.ProjectItems } | where { $_.Name -eq "Global.asax.cs" }
$customGlobalAsax.Open()
$customGlobalAsax.Document.Activate()
$customGlobalAsax.Document.Selection.SelectAll()
$customGlobalAsax.Document.Selection.Copy()
$a = [System.Windows.Forms.Clipboard]::GetText()
$a = $a -replace "using Company.Web.Mvc.ViewBase;","using Company.Web.Mvc.ViewBase;`r`nusing Company.Web.Address;"
[System.Windows.Forms.Clipboard]::SetText($a)
$customGlobalAsax.Document.Selection.Delete()
$customGlobalAsax.Document.Selection.Paste()

from what I can see, there is some problem with this line since it will return nothing:
$customGlobalAsax = $project.ProjectItems | ForEach-Object { $_.ProjectItems } | where { $_.Name -eq "Global.asax.cs" }
The following is my test:
$directory = dir *
$directory | foreach {$_.name}
The above run successfully.
But the following returns nothing:
$directory = dir *
$directory.name | foreach {$_.name}
I believe in the latter case $_.name represents $directory.name.name which doesn't exist.
So it seems like this line in your script
$customGlobalAsax = $project.ProjectItems | ForEach-Object { $_.ProjectItems } | where { $_.Name -eq "Global.asax.cs" }
should be changed to:
$customGlobalAsax = $project | ForEach-Object { $_.ProjectItems } | where { $_.Name -eq "Global.asax.cs" }