Unable to see my custom add-ons in a local packagerepository

Erik Martinsen

Vote:

Hi!

We have several add-on modules developed inhouse. We are currently installing the modules by "manual upload"

These modules are stored in a local NuGetServer, but we are not able to see the packages from EPIServer Add-ons manager

In Web.config I have added:

<episerver.packaging protectedVirtualPath="~/EPiServer/" >
<packageRepositories>
<add name="MyNuGetServer" url="http://10.130.1.244:82/guestAuth/app/nuget/v1/FeedService.svc" />
</packageRepositories>
</episerver.packaging>

In the nuspc file of the package I have added:

<tags>EPiServerModulePackage MyNuGetServer</tags>

I have used fiddler and EPIServer queries the service and reads the feed from the NuGet server.

My Add-on packages are in that feed.

Anyone knows what I how I can get my packages visible in Add-ons Manager ?

#69666

Apr 02, 2013 11:31

Dmytro Duk

Vote:

My guess is that add-on system decides that your add-on cannot be installed and that's why you don't see it in the UI. However, the same verification should be performed when you install the add-on using manual upload. So it sounds a bit strange if you can install the same packages manualy.

Could you enable the logging with debug level for add-on system and see how the system loads and verifies the packages? Add something like this in EPiServerLogging.config:

<?xml version="1.0" encoding="utf-8"?>
<log4net>
...

<appender name="outputDebugStringAppender" type="log4net.Appender.OutputDebugStringAppender" >
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="[%thread] %level %logger: %message%n" />
</layout>
</appender> 

<logger name="EPiServer.Packaging" additivity="false">
<level value="Debug" />
<appender-ref ref="outputDebugStringAppender" />
</logger>

... 
</log4net>

Here I use DebugView tool, but you can log it to the file.

#69671

Apr 02, 2013 12:48

Erik Martinsen

Vote:

Hi!

Sees like I had not verified that the package was installable.

When I fixed the .net45 bug, everything worked as intended.

(earlier I teseted with a package generated manually on my locale machine and not on the build server)

Thanks

ErikM

#69674

Apr 02, 2013 13:27