# Publish Elastic.Apm.AspNetFullFramework prerelease to NuGet

**URL:** <https://discuss.elastic.co/t/publish-elastic-apm-aspnetfullframework-prerelease-to-nuget/184299>\
**Category:** APM\
**Tags:** dotnet\
**Created:** [June 5, 2019, 8:08am UTC](https://discuss.elastic.co/t/publish-elastic-apm-aspnetfullframework-prerelease-to-nuget/184299 "2019-06-05T08:08:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![NeoX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/neox/32/47249_2.png) [@NeoX](https://discuss.elastic.co/u/NeoX)\
**Post date:** [June 5, 2019, 8:08am UTC](https://discuss.elastic.co/t/publish-elastic-apm-aspnetfullframework-prerelease-to-nuget/184299/1 "2019-06-05T08:08:31Z")

</div>

Could the alpha prerelease of `Elastic.Apm.AspNetFullFramework` be published to NuGet just as `Elastic.Apm.AspNetCore` already is? I'm actively using both and having to put the former in a local repo with the latter on [nuget.org](http://nuget.org) is an unnecessary overhead.

I tried to do it myself, but the package ID is already reserved.

---

<div class="post-metadata">

**Author:** ![GregKalapos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregkalapos/32/37205_2.png) [@GregKalapos](https://discuss.elastic.co/u/GregKalapos)\
**Post date:** [June 5, 2019, 8:34am UTC](https://discuss.elastic.co/t/publish-elastic-apm-aspnetfullframework-prerelease-to-nuget/184299/2 "2019-06-05T08:34:12Z")

</div>

Hi @NeoX

We’ll definitely publish that package, but currently it’s not in a stage where we would feel comfortable with it being an official package. Mostly because we still work on its the CI coverage, so at the moment we don’t even have test automation running with that project.

Once this is done and we feel that it’s good for making it preview, we’ll publish that package.

---

<div class="post-metadata">

**Author:** ![NeoX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/neox/32/47249_2.png) [@NeoX](https://discuss.elastic.co/u/NeoX)\
**Post date:** [June 5, 2019, 8:47am UTC](https://discuss.elastic.co/t/publish-elastic-apm-aspnetfullframework-prerelease-to-nuget/184299/3 "2019-06-05T08:47:57Z")

</div>

You don't think publishing it as an alpha prerelease won't disclaim those risks, though?

---

<div class="post-metadata">

**Author:** ![GregKalapos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregkalapos/32/37205_2.png) [@GregKalapos](https://discuss.elastic.co/u/GregKalapos)\
**Post date:** [June 5, 2019, 8:55am UTC](https://discuss.elastic.co/t/publish-elastic-apm-aspnetfullframework-prerelease-to-nuget/184299/4 "2019-06-05T08:55:05Z")

</div>

Not at this stage. We really don't feel that it's ready for being published even as alpha prerelease.

But I promise you we will give more love to it and we are definitely committed to publish a package with [ASP.NET](http://ASP.NET) auto instrumentation.

Currently we are busy making our current packages beta, once this is done, that package is on the top of our priority list.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 26, 2019, 4:55am UTC](https://discuss.elastic.co/t/publish-elastic-apm-aspnetfullframework-prerelease-to-nuget/184299/5 "2019-06-26T04:55:16Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.