studioshell Discussions Rss Feed

New Post: Getting access to Project Properties

gep13 — Mon, 06 May 2013 14:10:23 GMT

Gotcha, thinking about it, that makes sense.

I have added an issue to the backlog:

https://github.com/beefarino/studioshell-contrib/issues/7

New Post: Getting access to Project Properties

beefarino — Mon, 06 May 2013 13:10:58 GMT

Technically solution folders are projects to Visual Studio; the DTE:/solution/projects and dte:/solution/codemodel nodes include them. It is a PITA; I've considered adding custom -filter for dir at those nodes that would return specific types, but the recursive traversal is expensive. I'm more inclined to add a "get-project" cmdlet to ss.contrib that would match by name, language, project type, etc.

New Post: Nuget deployment of studioshell script

mterwoord — Sun, 05 May 2013 15:54:57 GMT

I want to have some VS extensions written using studioshell which are distributed using nuget. Is this possible out-of-the-box or do I need to make something myself for that?

(Ps. Great project!)

New Post: Getting access to Project Properties

gep13 — Sat, 04 May 2013 14:07:15 GMT

Hello again,

Ok, I have this working, to an extent, but now I am looking to extend it slightly more :)

Within a Solution, we sometimes use Solution Folders to group different projects together. I thought I had read that doing dir on dte:/Solution/Projects would return all the Projects within the Solution, regardless of their "Location", i.e. nested within a Solution Folder, but this doesn't seem to be the case. Did I pick this up wrong, or am I doing something incorrect?

Thanks

Gary

New Post: Getting access to Project Properties

gep13 — Sat, 04 May 2013 12:54:15 GMT

Hey Jim,

That did it! :-)

Completed script being:

dir | where { 
    Test-Path "$( $_.pspath )\ProjectProperties\WebApplication.StartWebServerOnDebug" 
} | foreach { 
    Set-Item "$( $_.pspath )\ProjectProperties\WebApplication.StartWebServerOnDebug" -value $false 
}

Thanks

Gary

New Post: Getting access to Project Properties

beefarino — Sat, 04 May 2013 11:54:42 GMT

Herp derp, by bad... I forgot that StudioShell doesn't return the item path from the ToString method of the DTE wrappers. No matter...

dir | where { Test-Path "$( $_.pspath )\ProjectProperties\WebApplication.StartWebServerOnDebug" }

See if that gets you moving. The $() in the string tells PowerShell to evaluate the expression when interpolating the string.

New Post: Getting access to Project Properties

gep13 — Fri, 03 May 2013 22:22:40 GMT

Hello there,

Thanks for getting back to me! Yes, this looks like exactly what I want, and it is essentially what I was trying, but I can't for the life of me get it to work.

I have a solution open in Visual Studio that has two Web Applications, and a Windows Application.

If I try to run the above script, I get no results returned. It seems to be the case that once piped through, the result of the dir, doesn't seem to be the correct "context", if that is the right word.

If I do the following:

cd DTE:\Solution\Projects\WebApplication1;
Test-Path ProjectProperties\WebApplication.StartWebServerOnDebug

I will get a result of True. And when I do:

cd DTE:\Solution\Projects\WindowsApplication1;
Test-Path ProjectProperties\WebApplication.StartWebServerOnDebug

I will get a result of false, which is exactly as expected.

However, even running this:

cd DTE:\Solution\Projects;
dir | where { Test-Path $_\ProjectProperties\WebApplication.StartWebServerOnDebug }

Returns no results.

I have tried all the various combinations of things that I can think of, but I can get anything to work.

Any ideas?

Thanks

Gary

New Post: Getting access to Project Properties

beefarino — Fri, 03 May 2013 14:07:52 GMT

I'm spitballing here, but based on our previous exchanges on this thread, I see no reason something like this wouldn't work:

cd DTE:\solution\projects;
dir | where { 
  test-path $_\ProjectProperties\WebApplication.StartWebServerOnDebug 
} | foreach {
  set-item $_\ProjectProperties\WebApplication.StartWebServerOnDebug -value $false #or $true
}

New Post: Getting access to Project Properties

gep13 — Mon, 29 Apr 2013 13:30:04 GMT

Hey,

Okay, I have to say, this has got me stumped!

I can't find a way to do the following:

For the given solution, enumerate all the Projects, and if that project is of type WebApplication, or rather, has the WebApplication.StartWebServerOnDebug property, set this property to false.

Any chance someone can provide an example of doing this?

Thanks

Gary

New Post: Getting access to Project Properties

gep13 — Sat, 27 Apr 2013 17:58:23 GMT

Hey,

Aw man, you have no idea! I keep thinking of more and more things that I can use StudioShell for :-)

That looks perfect, thanks! Now, a follow up question...

What would be the best way to select all of the WebApplication Projects from a given solution? We have a reasonably large solution, and there is a mixture of Windows Application, Web Applications, etc within the solution. Obviously, this property doesn't exist all project types.

Thanks

Gary

New Post: Getting access to Project Properties

beefarino — Sat, 27 Apr 2013 17:09:04 GMT

Hey again, you've been busy Gary...

You'll find those properties in the /projectproperties folder of the project; e.g.,:

dir DTE:\solution\projects\SuperAwesomeWebsite\ProjectProperties;

You can use set-item to set the value for any of the properties; the one you're after is "WebApplication.StartWebServerOnDebug:"
set-item DTE:\solution\projects\SuperAwesomeWebsite\ProjectProperties\WebApplication.StartWebServerOnDebug -value $false #or $true

New Post: No StudioShell-compatible hosts installed?

janbaer — Sat, 27 Apr 2013 04:33:57 GMT

Thank you very much! The setup runs now on my computer perfectly!

New Post: Getting access to Project Properties

gep13 — Fri, 26 Apr 2013 20:58:38 GMT

Hello,

When you have a project within a solution that is a "Web Application" project, there is a property called "Always Start When Debug". Having done:

$project = Get-Item .\WebApplication1

How would I go about getting access to this property?

Also, what is the best way of looking up the available properties, assuming that they aren't exposed directly through StudioShell?

Thanks

Gary

New Post: No StudioShell-compatible hosts installed?

beefarino — Thu, 25 Apr 2013 21:51:44 GMT

Sorry for the delay, but I've managed to fix the installer so that it now checks the registry for your installation paths. Please download the latest 1.5 release and see if this fixes your issue.

New Post: No StudioShell-compatible hosts installed?

janbaer — Mon, 08 Apr 2013 18:22:37 GMT

Cool! Thank you very much!

Best regards

Jan

New Post: No StudioShell-compatible hosts installed?

beefarino — Mon, 08 Apr 2013 17:52:28 GMT

Ah, okay - the installer looks for it under program files. I'll have to see what I can do to make this work for you... Give me a day and I'll have an update.

New Post: No StudioShell-compatible hosts installed?

janbaer — Mon, 08 Apr 2013 17:49:44 GMT

The complete path on my machine is: c:\Develop\VisualStudio\common7\ide\devenv.exe.

It's my personal folder structure to have all my devtools under C:\Develop.

New Post: No StudioShell-compatible hosts installed?

beefarino — Mon, 08 Apr 2013 15:21:17 GMT

Where is it installed on your machine? What is the complete path to devenv.exe?

New Post: No StudioShell-compatible hosts installed?

janbaer — Mon, 08 Apr 2013 15:18:44 GMT

Hello beefarino,

Visual Studio is installed on another location on my computer.

Do you expect it on ''c:\program files (x86)\Microsoft Visual Studio 11.0' ?

Best regards

Jan

New Post: No StudioShell-compatible hosts installed?

beefarino — Mon, 08 Apr 2013 14:29:31 GMT

Jan;

if you run this script in PowerShell, what is the output?

get-item 'c:\program files (x86)\Microsoft Visual Studio 11.0\common7\ide\devenv.exe' | select *