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.

Sign up for GitHub

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

Jump to bottom

OctoPack doesn't support new 2017 .csproj format #3822

Closed
msnelling opened this issue Sep 27, 2017 · 2 comments
Closed

OctoPack doesn't support new 2017 .csproj format #3822

msnelling opened this issue Sep 27, 2017 · 2 comments
Assignees
@benPearce1

Comments

@msnelling
Copy link

OctoPack doesn't support the new .csproj file format in Visual Studio 2017
@msnelling msnelling mentioned this issue Sep 27, 2017
Closed
@benPearce1
Copy link

benPearce1 commented Oct 3, 2017 •
edited
Loading

Hi,

We have this support on our radar, but don't have an ETA at this stage.
In the meantime, you could try running dotnet publish and then run octo.exe pack against the publish output folder.

I hope this helps.

For future reference, the best way to work through this is to use our support channel: http://octopus.com/support
We don't actively monitor this backlog for new issues as per our contributing guide.

Regards
Ben

0xced added a commit to 0xced/SbManager that referenced this issue Jun 5, 2018
@0xced
Convert solution to the new csproj format
d1c83bf 
Although the [documentation (Additions to the csproj format for .NET Core)][1] seems to imply that this is a .NET Core feature, it works with .NET Framework too and is much easier to maintain.

With this commit, the OctoPack feature is gone because the new .csproj format is not yet supported by OctoPack. Here is the [suggested workaround][2]:
> We have this support on our radar, but don't have an ETA at this stage.
In the meantime, you could try running `dotnet publish` and then run `octo.exe pack` against the publish output folder.

[1]: https://docs.microsoft.com/en-us/dotnet/core/tools/csproj
[2]: OctopusDeploy/Issues#3822 (comment)
0xced added a commit to 0xced/SbManager that referenced this issue Jun 5, 2018
@0xced
Convert solution to the new csproj format
6f47081 
Although the [documentation (Additions to the csproj format for .NET Core)][1] seems to imply that this is a .NET Core feature, it works with .NET Framework too and is much easier to maintain.

With this commit, the OctoPack feature is gone because the new .csproj format is not yet supported by OctoPack. Here is the [suggested workaround][2]:
> We have this support on our radar, but don't have an ETA at this stage.
In the meantime, you could try running `dotnet publish` and then run `octo.exe pack` against the publish output folder.

[1]: https://docs.microsoft.com/en-us/dotnet/core/tools/csproj
[2]: OctopusDeploy/Issues#3822 (comment)
0xced added a commit to 0xced/SbManager that referenced this issue Jun 6, 2018
@0xced
Convert solution to the new csproj format
6725784 
Although the [documentation (Additions to the csproj format for .NET Core)][1] seems to imply that this is a .NET Core feature, it works with .NET Framework too and is much easier to maintain.

With this commit, the OctoPack feature is gone because the new .csproj format is not yet supported by OctoPack. Here is the [suggested workaround][2]:
> We have this support on our radar, but don't have an ETA at this stage.
In the meantime, you could try running `dotnet publish` and then run `octo.exe pack` against the publish output folder.

[1]: https://docs.microsoft.com/en-us/dotnet/core/tools/csproj
[2]: OctopusDeploy/Issues#3822 (comment)

# Conflicts:
#	src/SbManager/SbManager.csproj
#	src/SbManager/packages.config
@lock
Copy link

lock bot commented Nov 24, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@benPearce1 benPearce1

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@msnelling @slewis74 @benPearce1