Rename projects to something more appropriate #182

Closed
gleno opened this Issue Feb 27, 2013 · 1 comment

Comments

Projects
None yet
3 participants

gleno commented Feb 27, 2013

I know this is a very minor thing, but it bothers my OCD.

Some of the projects are reusing code and target different frameworks, and are named for these targets rather than descriptively (for example the DotNet40 project). This causes confusion in solutions which include source for this project instead of referencing the Microsoft.WindowsAzure.Storage.dll.

MSDN guidelines for project naming can be found here. And I'll quote a relevant excerpt

Use Common Names for Projects and Assemblies
Your output assembly name should always match the project name from which it is generated. For example, you should be able to assume that an assembly called MyCompany.Utilities.Data.dll is generated by a project called MyCompany.Utilities.Data.

We reference this repository as a sub module, and pull updates quite often, so it wouldn't be practical to make changes from our side.

Member

jeffwilcox commented Nov 5, 2013

@gleno thanks, we've shared this feedback internally but for the time being are not planning any changes here. We have been chatting with the storage team however about how they are going to structure their source enlistment and repositories on GitHub in the future, so there may be a chance to fix this still - just nothing planned today.

Closing as the feedback has been shared - thanks!

jeffwilcox closed this Nov 5, 2013

jeffreyjirwin was unassigned by gleno Apr 3, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment