[
https://issues.apache.org/jira/browse/NPANDAY-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930100#action_12930100
]
Adelita L. Padilla edited comment on NPANDAY-335 at 11/9/10 9:22 AM:
---------------------------------------------------------------------
Update:
Changing the path of the <Assembly> tag to point to the location of the
NPanday.VisualStudio.Addin.dll in the local repository (since pab folder
doesn't exist) still doesn't solve the problem because it's unable to look for
some dependencies (see list of dependencies below).
In the previous code (pab folder still exists), NPanday can be successfully
loaded in Visual Studio because the folder (
C:\Users\{username}\.m2\pab_\gac_msil\NPanday.VisualStudio.Addin\{version}__npanday.visualstudio
) where the dll in the <Assembly> tag of the .addin file is located, also
contains the ff dlls:
* NPanday.Artifact.dll
* NPanday.Logging.dll
* NPanday.Model.Pom.dll
* NPanday.Model.Settings.dll
* NPanday.Plugin.dll
* NPanday.ProjectImporterEngine.dll
* NPanday.Utils.dll
* NPanday.VisualStudio.Addin.dll
* NPanday.VisualStudio.dll
* NUnit.Framework.dll
These dlls need to be present in the folder where the addin dll is located.
Here's my proposal for the fix of this issue:
* when running the vsinstaller command, it behaves like that of the npanday msi
installer
- it creates a dir where the above mentioned libraries are located (e.g
C:\Program Files\NPanday\bin )
- <Assembly> tag in the addin file will point to this --> C:\Program
Files\NPanday\bin\NPanday.VisualStudio.Addin.dll
Any thoughts/suggestions?
Thanks!
was (Author: apadilla):
Update:
Changing the path of the <Assembly> tag to point to the location of the
NPanday.VisualStudio.Addin.dll in the local repository (since pab folder
doesn't exist) still doesn't solve the problem because it's unable to look for
some dependencies (see list of dependencies below).
In the previous code (pab folder still exists), NPanday can be successfully
loaded in Visual Studio because the folder (
C:\Users\{username}\.m2\pab_\gac_msil\NPanday.VisualStudio.Addin\{version}__npanday.visualstudio
) where the dll in the <Assembly> tag of the .addin file, also contains the ff
dlls:
* NPanday.Artifact.dll
* NPanday.Logging.dll
* NPanday.Model.Pom.dll
* NPanday.Model.Settings.dll
* NPanday.Plugin.dll
* NPanday.ProjectImporterEngine.dll
* NPanday.Utils.dll
* NPanday.VisualStudio.Addin.dll
* NPanday.VisualStudio.dll
* NUnit.Framework.dll
These dlls need to be present in the folder where the addin dll is located.
Here's my proposal for the fix of this issue:
* when running the vsinstaller command, it behaves like that of the npanday msi
installer
- it creates a dir where the above mentioned libraries are located (e.g
C:\Program Files\NPanday\bin )
- <Assembly> tag in the addin file will point to this --> C:\Program
Files\NPanday\bin\NPanday.VisualStudio.Addin.dll
Any thoughts/suggestions?
Thanks!
> NPanday on Visual Studio only starts on Debug Mode
> --------------------------------------------------
>
> Key: NPANDAY-335
> URL: https://issues.apache.org/jira/browse/NPANDAY-335
> Project: NPanday
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Joe Ocaba
> Assignee: Joe Ocaba
> Fix For: 2.0
>
> Attachments: 335.patch
>
>
> There is a problem with the addin in starting from Visual Studio, but the
> commands from the command line are working fine. It works fine if you run
> NPanday under debug mode
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
