OS Version: Windows 10 x64
WMF Version: 5.0
Impact: Major inconvenience
Symptom:
PowerShell Studio will not provide Primal Sense for custom libraries of any complexity, when typing the type-name (In New-Object calls, when casting or when defining parameter types).
Reproducibility:
Create a simple custom type like this:
- $source = @"
- using System;
- namespace Test
- {
- public class Test
- {
- public string foo;
- public int bar;
- }
- }
- "@
- Add-Type -TypeDefinition $source -OutputAssembly "C:\temp\test.dll"
- Add-Type "C:\temp\test.dll"
- New-Object Test|
Additional Testing done:
- Restarting PSS after creating library and adding reference: The entry under "Assemblies" was gone, no PS given. Manually adding reference would do nothing.
- Adding a complex library with or without comments: No Success
- Adding library adding "System" namespaced types: No success
- PSS still recognizes valid types in brackets (when casting or declaring parameters)
-- PSS provides Primal Sense for Variables of custom types (after casting / parameter typing)
-- PSS provides Primal Sense for static methods and properties