search

dotnet / orleans

Cloud Native application framework for .NET
https://docs.microsoft.com/dotnet/orleans
MIT License
10.07k stars 2.03k forks source link

Consider renaming dlls \ exes \ namespaces #25

Closed jkonecki closed 8 years ago

jkonecki commented 9 years ago

Not as simple as changing NuGet package names but I think this should be discussed before wider adoption. Those are breaking changes and it's better to bite the bullet now.

I would like to suggest we change Orleans dlls \ exes to Microsoft.Orleans.xxx. and change the namespaces accordingly.

What are your thoughts?

jesuspsalas commented 9 years ago

+1 to bite the bullet as soon as possible on this!

From: Jakub Konecki [mailto:notifications@github.com] Sent: lunes, 26 de enero de 2015 6:37 To: dotnet/orleans Subject: [orleans] Consider renaming dlls \ exes \ namespaces (#25)

Not as simple as changing NuGet package names but I think this should be discussed before wider adoption. Those are breaking changes and it's better to bite the bullet now.

I would like to suggest we change Orleans dlls \ exes to Microsoft.Orleans.xxx. and change the namespaces accordingly.

What are your thoughts?

— Reply to this email directly or view it on GitHubhttps://github.com/dotnet/orleans/issues/25.

sergeybykov commented 9 years ago

I'm not sure about this one. It would be much more disruptive for all the people that already reference the binaries, internally and externally. NuGet packages don't have that problem, as we never published them.

jkonecki commented 9 years ago

Sergey, I do understand the knock-on effect. I would just like to avoid the pain that Azure Storage Client or EntityFramework caused with namespace / dll changes once the usage was much wider...

Again, it's just a suggestion to consider as it will be more and more difficult to implement as the time goes.

overeemm commented 9 years ago

I would encourage the rename! We already reference the dll's from the SDK. Changing everything to nuget is already work, so I do not mind the rename of namespaces and DLL's.

richorama commented 9 years ago

My two pence - in a cost/benefit analysis, I'm not sure I see much benefit, but there is potentially quite a bit of cost.

Theoretical question; how permanent is the name 'Orleans'? Will Orleans be renamed to 'Microsoft Virtual Actor Model for .NET' at some point?

sergeybykov commented 9 years ago

It doesn't look likely that 'Orleans' will get renamed to something like 'Microsoft Virtual Actor Model for .NET'.

akoeplinger commented 9 years ago

I'd say I'm in favor of the rename, if only to make it consistent with all the other "next-gen" MS frameworks like ASP.NET5 (Microsoft.AspNet.*), Roslyn (Microsoft.CodeAnalysis.*) etc.

MovGP0 commented 9 years ago

the demon Legion would be a fitting name too. ("My name is Legion: for we are many")

However, something like Microsoft.Actors might be a more consistent namespace.

ym2c

sergeybykov commented 8 years ago

We'll stick with the current name.