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

No *.sln file found #5

Open
ilkerinanc opened this issue Feb 23, 2014 · 3 comments
Open

No *.sln file found #5

ilkerinanc opened this issue Feb 23, 2014 · 3 comments

Comments

@ilkerinanc
Copy link

Hi,

I have an ASP.NET application with Global.asax file. And my application does not have an .sln file. When I try to push my app to heroku, I got the following error:

-----> Fetching custom git buildpack... done
-----> ASP.NET app detected
-----> Bundling XSP v3.0.11
Fetching 3.0.11 @ http://s3.amazonaws.com/mono-dependencies/xsp-3.0.11.tar.gz
-----> Bundling Mono v3.2.8
Fetching Mono v3.2.8 @ http://s3.amazonaws.com/mono-dependencies/mono-3.2.8.tar.gz
Copying xsp libraries to the GAC
-----> Fetching fixed NuGet.targets
-----> No *.sln file found

 !     Push rejected, failed to compile ASP.NET app

From what I understand from https://github.com/friism/heroku-buildpack-mono/blob/master/bin/compile compiler looks for an .sln file and when it can not find it terminates the push.

But in the readme file it says The buildpack will detect your app as ASP.NET if it has the file global.asax in the root or at one directory depth or as .NET if it has a .sln file.

How can we solve this?
Thanks

@friism
Copy link
Owner

friism commented Feb 23, 2014

Hm, that's a bug in the docs, actually - currently a solution file is required so that xbuild can be invoked. What are you trying to build?

@ilkerinanc
Copy link
Author

Well, to be honest I don't have any ASP.NET experience, and I'm trying to push a client's application to heroku. All I know is it is an ASP.NET MVC 4.0 application. Application's tree looks like this:

screen shot 2014-02-23 at 3 15 38 pm

@friism
Copy link
Owner

friism commented Feb 23, 2014

Hm, it looks like it's been compiled already - that scenario is not really supported with the way the buildpack is currently implemented, I'm afraid. You push source code, it gets built and then deployed.

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