+1 800 256 3608 (toll-free in North America) or +49 7531 90 60 10| service@combit.com

Remove version from namespace


(combit - Webmaster) #1

The current List&Label version is included in the namespace. I.e.

combit.ListLabel20
combit.ListLabel20.ListLabel

While there might be some good reasons to do it this way this is pretty much inque for every other third party library I know in the .NET eco system.

Let's say I am planning to write a DataProvider or any other List&Label extension and publish it on NuGet I have to compile it agains every single ListLabel version because

combit.ListLabel20.ListLabel != combit.ListLabel21.ListLabel

And every time a new version comes out it has to be created again even if it would work out of the box without any modification.

I would love to see List&label having just combit.ListLabel as a namespace in the future.

(combit - Jochen Bartlau) #2

Absolutely valid request, however we have many customers who work with multiple versions in parallel. Think of large applications that are updated step by step. Changing to one namespace would prevent this from working. However I’m curious to read what others think about this.


(Juergen Steinblock) #3

Since you already deploy multiple versions of List&Label maybe it would be a good solution to keep everything as usual but for nuget switch to a more modular approach with a combit.listlabel.core package (without version in it’s namespace) and multiple extension packages (combit.listlabel.dataproviders / combit.listlabel.mysqldataprovider / combit.listlabel.sqlitedataprovider) with it’s own dependencies.


(Stefan Kriebitzsch) #4

Hello,

I absolutely aggree with @Juergen_Steinblock.
In my web project I need only the listlabelXY.dll and not the listlabelXY.web.dll. Because we use the browser integrated pdf UI. Also I use only one data provider. So I would prefer modular nuget packages.

I think, the version number is also not neccessary in the assembly name.


(combit - Jochen Bartlau) #5

I’ll put the “modular package” approach on the radar of our deployment team. However, we’ll probably not be able to remove the version number from the assemblies and namespaces as many fellow developers would kill us if we removed the possibility to have several versions in parallel :fearful:.