Martin Machacek

Same for Microsoft.Graph.xml v4.6 - 29.7 MB (31,194,770 bytes) v5.1 - 61.9 MB (64,972,960 bytes) I suspect that very long namespaces have effect on the size of dll and xml....

@silentdevnull https://github.com/microsoftgraph/msgraph-sdk-dotnet/issues/1874 Looks like the target version with a fix is v6.

From my investigation, there is a lot of duplicated classes with the same name but under different namespaces. I've comparing v4.54 and v5.9 **version 4.54** In version 4.54 there is...

Yes, the issue is that there is only one single assembly that contains **_builders_** for thousands endpoints. Real use case is that an app is calling only a small subset...

@pschaeflein Sure, I can generate a SDK for Graph API with Kiota by myself, but the whole process is quite complicated. Metadata for OpenAPI spec are preprocessed several times, but...

> ## Self-served clients > No application needs all Graph operations and endpoints, while a pre-packaged SDK makes things straightforward to discover and consume, it brings its trade-off. For scenarios...

@Kane-Baden Thanks for info. I would like to avoid any workaround because it's time consuming to write workaround and then remove it. @Stephan-Hoffmann Be aware that there is another issue...

I would expect that msgraph-sdk-dotnet team will test workbook api properly. v5 was released more than one month ago and it still doesn't work.

@andrueastman Is there any estimate (weeks, months) when it will be fixed? I would like to use v5 for a new project but I'm afraid that v4 is only version...

@maisarissi Kindly reminder, workbook API is not supported since v5 has been released.