PowerShell installation - missing file
-
I started messing around with Windows PowerShell[^]. Quite impressive. I have a problem, though. It seems that the file
System.Management.Automation.dllis missing (the installation completed successfully). The thing still works, but I cannot register cmdlets (the compiler says it cannot find the assembly, and it's true - no assemblies in the installation path (system32\windowspowershell\v1.0)). I couldn't find anything useful on the net. Any advice? Did anyone notice the same? Thanks.________________________________________________ Personal Blog [ITA] - Tech Blog [ENG] Developing ScrewTurn Wiki 1.1 (1.0.7 is out)
Dario Solera wrote:
System.Management.Automation.dll
Does.Anyone.Else.Wonder.How.Long.Filenames.Will.Get.Before.MS.Is.Satisfied.dll? [edit] I just love how people abuse the voting system now. Yeah, like this post is inappropriate and needs to be filtered. [/edit]
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
-
Dario Solera wrote:
System.Management.Automation.dll
Does.Anyone.Else.Wonder.How.Long.Filenames.Will.Get.Before.MS.Is.Satisfied.dll? [edit] I just love how people abuse the voting system now. Yeah, like this post is inappropriate and needs to be filtered. [/edit]
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
-
Dario Solera wrote:
System.Management.Automation.dll
Does.Anyone.Else.Wonder.How.Long.Filenames.Will.Get.Before.MS.Is.Satisfied.dll? [edit] I just love how people abuse the voting system now. Yeah, like this post is inappropriate and needs to be filtered. [/edit]
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
Jeremy Falcon wrote:
Doea.Anyone.Else.Wonder.How.Long.Filenames.Will.Get.Before.MS.Is.Satisfied.dll?
:-D
________________________________________________ Personal Blog [ITA] - Tech Blog [ENG] Developing ScrewTurn Wiki 1.1 (1.0.7 is out)
-
What is
MAX_PATH? Like, 250 chars or something? Sure there are ways around it, but i doubt most programs support them terribly well...Shog9 wrote:
What is MAX_PATH? Like, 250 chars or something?
I thought it was bumped up to 512 for newer versions of Winders. Have to double-check that though as my brain tends to play little games on me these days. Still, if the filename is 5 miles long, you're just lessening the amount of dirs your program is gonna access before it just starts barfing.
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
-
Dario Solera wrote:
System.Management.Automation.dll
Does.Anyone.Else.Wonder.How.Long.Filenames.Will.Get.Before.MS.Is.Satisfied.dll? [edit] I just love how people abuse the voting system now. Yeah, like this post is inappropriate and needs to be filtered. [/edit]
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
Jeremy Falcon wrote:
System.Management.Automation.dll
Meh, that's a mere 33 characters. IMO, I'd rather have a descriptive name like that than msmngmntautomtn.dll
Tech, life, family, faith: Give me a visit. I'm currently blogging about: God-as-Judge, God-as-Forgiver The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Jeremy Falcon wrote:
System.Management.Automation.dll
Meh, that's a mere 33 characters. IMO, I'd rather have a descriptive name like that than msmngmntautomtn.dll
Tech, life, family, faith: Give me a visit. I'm currently blogging about: God-as-Judge, God-as-Forgiver The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
Judah Himango wrote:
IMO, I'd rather have a descriptive name like that than msmngmntautomtn.dll
Maybe I'm old school, but I don't see using standard, common abbreviations as being non-descriptive.
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
-
Judah Himango wrote:
IMO, I'd rather have a descriptive name like that than msmngmntautomtn.dll
Maybe I'm old school, but I don't see using standard, common abbreviations as being non-descriptive.
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
I bet you're the same guy who coded all these functions I see in some libraries....chkcmdlenstx, showerrlenonfnferr... ;) I know, you said "standard, common", but standard and common is relative. In my experience, once you start abbreviating everything, it only adds to confusion. Unless you're hitting a real problem with path lengths -- and jeez, the few extra characters is a drop in the 255 max bucket -- it's better to use descriptive names. Just my opinion. Jeremy, outside of typing fewer characters and lessening the [rare] likelihood of path too long errors, are there any other benefits to abbreviating everything? I guess my main problem is that it gets too cryptic over time and only adds to confusion later on.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: God-as-Judge, God-as-Forgiver The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
I started messing around with Windows PowerShell[^]. Quite impressive. I have a problem, though. It seems that the file
System.Management.Automation.dllis missing (the installation completed successfully). The thing still works, but I cannot register cmdlets (the compiler says it cannot find the assembly, and it's true - no assemblies in the installation path (system32\windowspowershell\v1.0)). I couldn't find anything useful on the net. Any advice? Did anyone notice the same? Thanks.________________________________________________ Personal Blog [ITA] - Tech Blog [ENG] Developing ScrewTurn Wiki 1.1 (1.0.7 is out)
Reference assemblies are installed into %program files%\Reference Assemblies\Microsoft\<Product>\v<Version>. I just looked at an install for WPS files at C:\Program Files\Reference Assemblies\Microsoft\WindowsPowerShell\v1.0 and find the following: 09/28/2006 02:49 PM 139,264 Microsoft.PowerShell.Commands.Management.dll 09/28/2006 02:49 PM 294,912 Microsoft.PowerShell.Commands.Utility.dll 09/28/2006 02:49 PM 200,704 Microsoft.PowerShell.ConsoleHost.dll 09/28/2006 02:49 PM 65,536 Microsoft.PowerShell.Security.dll 09/28/2006 02:49 PM 1,564,672 System.Management.Automation.dll 5 File(s) 2,265,088 bytes 2 Dir(s) 48,475,697,152 bytes free Tom Archer Program Manager - Windows SDK Compilers and Tools MICROSOFT
-
I bet you're the same guy who coded all these functions I see in some libraries....chkcmdlenstx, showerrlenonfnferr... ;) I know, you said "standard, common", but standard and common is relative. In my experience, once you start abbreviating everything, it only adds to confusion. Unless you're hitting a real problem with path lengths -- and jeez, the few extra characters is a drop in the 255 max bucket -- it's better to use descriptive names. Just my opinion. Jeremy, outside of typing fewer characters and lessening the [rare] likelihood of path too long errors, are there any other benefits to abbreviating everything? I guess my main problem is that it gets too cryptic over time and only adds to confusion later on.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: God-as-Judge, God-as-Forgiver The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
Judah Himango wrote:
I know, you said "standard, common", but standard and common is relative. In my experience, once you start abbreviating everything, it only adds to confusion.
If it adds confusion, then you're not using standard abbreviations. :)
Judah Himango wrote:
Unless you're hitting a real problem with path lengths -- and jeez, the few extra characters is a drop in the 255 max bucket
On a typical WinXP install, when you get folders like this... C:\Documents and Settings\Jeremy\Local Settings\Application Data\Identities\{D7632ACE-16CE-44AD-9615-35E18FF3CB5E}\Microsoft\Outlook Express Yes, it's 140 chars and not the limit, but my point is A: using shorthand let's you take it even further with less worries and B: it's not cryptic unless someone makes it out to be. And it's for damn sure not as cryptic as using a GUID for a folder name. :laugh: Also, let's not forget to mention if your app does depends on a structure, having short-handed names, does make a bit more portable.
Judah Himango wrote:
I guess my main problem is that it gets too cryptic over time and only adds to confusion later on.
There is nothing more confusing about something along of lines of SysAdmin compared to System.Administration.
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
-
Judah Himango wrote:
I know, you said "standard, common", but standard and common is relative. In my experience, once you start abbreviating everything, it only adds to confusion.
If it adds confusion, then you're not using standard abbreviations. :)
Judah Himango wrote:
Unless you're hitting a real problem with path lengths -- and jeez, the few extra characters is a drop in the 255 max bucket
On a typical WinXP install, when you get folders like this... C:\Documents and Settings\Jeremy\Local Settings\Application Data\Identities\{D7632ACE-16CE-44AD-9615-35E18FF3CB5E}\Microsoft\Outlook Express Yes, it's 140 chars and not the limit, but my point is A: using shorthand let's you take it even further with less worries and B: it's not cryptic unless someone makes it out to be. And it's for damn sure not as cryptic as using a GUID for a folder name. :laugh: Also, let's not forget to mention if your app does depends on a structure, having short-handed names, does make a bit more portable.
Judah Himango wrote:
I guess my main problem is that it gets too cryptic over time and only adds to confusion later on.
There is nothing more confusing about something along of lines of SysAdmin compared to System.Administration.
Jeremy Falcon A multithreaded, OpenGL-enabled application.[^]
I agree about SysAdmin example. Another good example is RegEx versus RegularExpression. My problem is the fact that people tend to take things too far, abbreviating everything, making a cryptic, unreadable mess of things. That's what I don't like, and without having some sort of hard line rule as far as what is "common knowledge", it's wide open for abuse.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: God-as-Judge, God-as-Forgiver The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Reference assemblies are installed into %program files%\Reference Assemblies\Microsoft\<Product>\v<Version>. I just looked at an install for WPS files at C:\Program Files\Reference Assemblies\Microsoft\WindowsPowerShell\v1.0 and find the following: 09/28/2006 02:49 PM 139,264 Microsoft.PowerShell.Commands.Management.dll 09/28/2006 02:49 PM 294,912 Microsoft.PowerShell.Commands.Utility.dll 09/28/2006 02:49 PM 200,704 Microsoft.PowerShell.ConsoleHost.dll 09/28/2006 02:49 PM 65,536 Microsoft.PowerShell.Security.dll 09/28/2006 02:49 PM 1,564,672 System.Management.Automation.dll 5 File(s) 2,265,088 bytes 2 Dir(s) 48,475,697,152 bytes free Tom Archer Program Manager - Windows SDK Compilers and Tools MICROSOFT
Tom Archer - MSFT wrote:
Reference assemblies are installed into %program files%\Reference Assemblies\Microsoft\\v.
I don't have the Reference Assemblies directory. :~
________________________________________________ Personal Blog [ITA] - Tech Blog [ENG] Developing ScrewTurn Wiki 1.1 (1.0.7 is out)
-
Tom Archer - MSFT wrote:
Reference assemblies are installed into %program files%\Reference Assemblies\Microsoft\\v.
I don't have the Reference Assemblies directory. :~
________________________________________________ Personal Blog [ITA] - Tech Blog [ENG] Developing ScrewTurn Wiki 1.1 (1.0.7 is out)
I've never heard of anyone not having that folder installed. Email me offline and I'll help you.
Tom Archer (blog) Program Manager - Windows SDK Compilers and Tools MICROSOFT