Project Restructure

[michaellwest]

What are you thoughts on structuring the project with something like this?

Cognifide.Sitecore - Contains all the sitecore integration code
Cognifide.PowerShell - Contains all the powershell integration code
Cognifide.Web - Contains the remaining code such as App_Config, sitecore, etc.
Solution Folder - Contains Data, and other related items

[AdamNaj]

For me personally I think this would cause a bit of confusion.
I'm usually attaching the PS project to another Sitecore solution that already has a number of "Cognifide.*" stuff in it, so this would be intermixed with the rest of the mess :)

I was thinking about dividing it differently some time ago though.
Since all this project does are 2 basic things:

• integration between Sitecore and PowerShell (ISE, provider, integration bits - those are part of the same story and should stick together).
• provide additional commandlets

I was thinking about splitting some of the commandlets into separate projects. The reason for it would be basically:

• I don't like the analytics torrent of commandlets there - additionally those can easily become a problem once Sitecore changes schema for the database. (basically future proofing against obsolescence)
• Potentially when we add commandlets that make use of the Sitecore 7 new functionality, we still want the core to be working on Sitecore 6.x, so that we don't remove a large pack of the potential user base. (but we are not there yet).

[michaellwest]

So are you thinking this would be something to put on the back burner for a while?

[AdamNaj]

Yeah, I don't see a clear benefit in this at this moment yet.