Question about PowerShell and .NET assemblies

Posted By: mstefan | Feb 11th, 2007 @ 4:16 AM
page 1 of 1
Comments: 5 | Views: 5119
#Feb 11th, 2007 @ 4:16 AM
mstefan
mstefan
Windows SDK coders do it without a .NET
PowerShell has the ability to load an assembly and create an instance of a class; is there a way for the assembly to know that it has been loaded in PS rather than, for example, as a reference in a Windows Forms based application?
#Feb 11th, 2007 @ 4:18 AM
mstefan
mstefan
Windows SDK coders do it without a .NET

[Too quick clicking the wrong button there...]

#Feb 11th, 2007 @ 5:10 AM
Yggdrasil
Yggdrasil
Pour me a cab, 'cause I can't drink no more.
How about this:

Assembly.GetEntryAssembly().GetName().Name == "PowerShell";

Is that what you're looking for?

#Feb 11th, 2007 @ 6:24 AM
mstefan
mstefan
Windows SDK coders do it without a .NET
Yggdrasil wrote:
How about this:

Assembly.GetEntryAssembly().GetName().Name == "PowerShell";

Is that what you're looking for?



Unfortunately that won't work. GetEntryAssembly returns null, presumably because the assembly is being loaded from unmanaged code.

It looks like I'm going to have to use an interop hack and call GetModuleFileName, but I'd prefer to not have to do that.
#Feb 11th, 2007 @ 7:21 AM
Yggdrasil
Yggdrasil
Pour me a cab, 'cause I can't drink no more.
mstefan wrote:

Yggdrasil wrote: How about this:

Assembly.GetEntryAssembly().GetName().Name == "PowerShell";

Is that what you're looking for?



Unfortunately that won't work. GetEntryAssembly returns null, presumably because the assembly is being loaded from unmanaged code.

It looks like I'm going to have to use an interop hack and call GetModuleFileName, but I'd prefer to not have to do that.


Process.GetCurrentProcess().MainModule.FileName?

#Feb 11th, 2007 @ 9:18 AM
mstefan
mstefan
Windows SDK coders do it without a .NET
The same basic difference there. My issue isn't so much with interop as having to use "magic strings" like the module filename to determine what loaded the assembly. It looks like the solution is to get the module name and version info and do a bunch of sanity checks.

I guess what I'm really driving at is I'd like some way to reliably ask "Am I being loaded in a script, not a compiled executable?" so that certain decisions could be made about behavior, default property values and licensing.
page 1 of 1
Comments: 5 | Views: 5119
Microsoft Communities