Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File structure changes when publishing #48

Open
rodrigopina360 opened this issue Mar 20, 2023 · 5 comments
Open

File structure changes when publishing #48

rodrigopina360 opened this issue Mar 20, 2023 · 5 comments
Assignees

Comments

@rodrigopina360
Copy link

Hello! I have come across a problem I've tried to fix to avail. I have a project with your nuget, and when built, copies it's executable to the root of the project, which is the expected behavior, but when published, the executable is moved to a newly created file structure "packages/PDFtoPrinter.1.5.0/build". I've found no way to override this behavior, so that the executable is placed at the root of the project.
As I have multiple other nugets installed, and none display this issue, I believe it might be a problem with this specific nuget, but would like some confirmation, and if so, what alternatives could be achieved to get working functionality when published.

@svishnevsky svishnevsky self-assigned this Mar 21, 2023
@svishnevsky
Copy link
Owner

Hi @Pinossaur

Thanks for reporting the issue. Could you please provide the version of .net framework you use and type of the application (console, web. desktop etc).

@rodrigopina360
Copy link
Author

I'm using .net framework 4.6.1 on a WPF desktop application

@svishnevsky
Copy link
Owner

Thanks @Pinossaur !

Just to confirm, do you publish to a local folder? Is the package installed to the WPF project itself or some library?

I've run tests and "setup.exe" copies files properly to me:
image

So I need a little bit more information from you to reproduce your case.

@rodrigopina360
Copy link
Author

Yeah, I indeed publish to a local folder, and have the package installed to the project itself. Besides that the only thing to note is that ClickOnce is used.

@svishnevsky
Copy link
Owner

Sorry @Pinossaur , still can't reproduce your issue. Could you please share the "csproj" file of yours with me? This might help to reproduce the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants