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

Build project failure #4

Open
kurtwilbies opened this issue Jun 13, 2017 · 11 comments
Open

Build project failure #4

kurtwilbies opened this issue Jun 13, 2017 · 11 comments
Labels

Comments

@kurtwilbies
Copy link

I tried to build the project in vs 2017 but I keep getting errors (assembly testing fake). Can you please build the project and release it, otherwise this is a useless repo.

@WillStrohl
Copy link
Member

Can you please provide more details about what is happening when you build?

@kurtwilbies
Copy link
Author

kurtwilbies commented Jun 13, 2017

Error relating to Microsoft.QualityTools.Testing.Fakes. See for a fix https://blogs.msdn.microsoft.com/visualstudioalm/2014/11/23/avoiding-visual-studio-fakes-build-break/. Can you publish an install package of hotcakes?

@kingjordan
Copy link

This may be an issue with what version of visual studio you are running. https://www.visualstudio.com/vs/compare/
fakes is for use with enterprise, so if you run professional you won't be able to build this project
this is a reference for anyone else who might end up here

@WillStrohl
Copy link
Member

@kurtwilbies @kingjordan We've always been using VS Enterprise, so it was far too easy to include an incompatible feature. Do you have any suggestions to make it more compatible with other VS editions?

@kingjordan
Copy link

I have only used professional and I have never tried to work on an enterprise solution from an outside source, so I don't think I can help you here

@WillStrohl
Copy link
Member

Well, we'll keep this open for now to see if anyone comes up with a suggestion. We didn't intend for there to be any features that are incompatible with other editions of VS, so we'd like to address that as soon as we can.

@BhawanaPokhariya
Copy link

I tried to build the project in vs 2015 (using Enterprise) ,but keep getting errors.
And is this solution will work with DNN 8 ?

@WillStrohl
Copy link
Member

@BhawanaPokhariya Could you please provide specific details about the errors you're receiving? If they're different than what you see in this issue, please provide those details in a new issue. And, yes, Hotcakes works in DNN 8 and 9.

@Navilois
Copy link
Contributor

VS2019 Community
Hotcakes Core 03.02.00 Release

This is the output of errors when Rebuilding the solution:

  • Error CS0234 The type or namespace name 'Fakes' does not exist in the namespace 'DotNetNuke.Entities.Profile' (are you missing an assembly reference?) Hotcakes.Commerce.Tests D:\Eigene Docs\Visual Studio 2019\Projects\Hotcakes-core-releases-03.02.00\Libraries\Hotcakes.Commerce.Tests\ContactService\AffiliateTest.cs 29 Active
  • Error CS0234 The type or namespace name 'QualityTools' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?) Hotcakes.Commerce.Tests D:\Eigene Docs\Visual Studio 2019\Projects\Hotcakes-core-releases-03.02.00\Libraries\Hotcakes.Commerce.Tests\ContactService\AffiliateTest.cs 35 Active
  • Error CS0234 The type or namespace name 'Fakes' does not exist in the namespace 'Hotcakes.Commerce.Data.EF' (are you missing an assembly reference?) Hotcakes.Commerce.Tests D:\Eigene Docs\Visual Studio 2019\Projects\Hotcakes-core-releases-03.02.00\Libraries\Hotcakes.Commerce.Tests\HotcakesApplicationTest.cs 28 Active
  • Error CS0234 The type or namespace name 'QualityTools' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?) Hotcakes.Commerce.Tests D:\Eigene Docs\Visual Studio 2019\Projects\Hotcakes-core-releases-03.02.00\Libraries\Hotcakes.Commerce.Tests\HotcakesApplicationTest.cs 30 Active
  • Warning The referenced component 'Hotcakes.Commerce.Dnn.Fakes' could not be found. Hotcakes.Commerce.Tests
  • Warning The referenced component 'Microsoft.QualityTools.Testing.Fakes' could not be found. Hotcakes.Commerce.Tests
  • Warning Could not resolve this reference. Could not locate the assembly "Hotcakes.Commerce.Dnn.Fakes". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Hotcakes.Commerce.Tests
  • Warning The referenced component 'Hotcakes.Commerce.Fakes' could not be found. Hotcakes.Commerce.Tests
  • Warning The referenced component 'DotNetNuke.7.3.1.21.Fakes' could not be found. Hotcakes.Commerce.Tests
  • Warning Could not resolve this reference. Could not locate the assembly "Microsoft.QualityTools.Testing.Fakes". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Hotcakes.Commerce.Tests
  • Warning Could not resolve this reference. Could not locate the assembly "DotNetNuke.7.3.1.21.Fakes". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Hotcakes.Commerce.Tests
  • Warning Could not resolve this reference. Could not locate the assembly "Hotcakes.Commerce.Fakes". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Hotcakes.Commerce.Tests
  • Warning Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: Hotcakes.Modules

@parasdaryanani
Copy link
Contributor

@Navilois Hotcakes only builds with Enterprise versions of Visual Studio, due to usage of Fakes, which are an enterprise feature. At some point these should be removed, since most OSS developers will not have access to visual studio enterprise.

@WillStrohl
Copy link
Member

You can work around this by not including the tests project in the build process.

WillStrohl pushed a commit that referenced this issue Jan 10, 2023
WillStrohl pushed a commit that referenced this issue Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

6 participants