YAFLogo

Posted by: hismightiness - Friday, 16 December 2016 01:11:27
I'm trying to get up and running with the DNN module solution locally so I can work on some stuff that's critical to a project, and it seems it's missing a lot of dependencies. I forked and began as usual with a new project. Unfortunately, there's no direction in the project or wiki on how to get started with this (that I could find). First, I found that it was looking for and missing the actual YAFNET solution/projects, so I added those, but I'm thinking I need to ignore those in the gitignore later. Now, those are found when I open the solution, but it's still missing the ServiceStack projects after adding the YAFNET source. I see the ServiceStack folder in the bootstrap branch, but not sure I should be developing against that. Is ServiceStack simply not checked in to master right now or something? How should I safely proceed? Ideally, I'd like to in the very least find out if there's a way to open up the DNN implementation to see all security roles - even if it's not going to be accepted into the core implementation.

Posted by: tha_watcha - Friday, 16 December 2016 16:14:46
Service Stack is added via Nuget. So you only need to recompile or do a Nuget Package restore.

Posted by: hismightiness - Friday, 16 December 2016 18:20:19
Oh really? I was reading that ServiceStack was included into the solution because it was modified to support some specific needs of YAFNET. Did that change? Thanks for your reply.

Posted by: hismightiness - Friday, 16 December 2016 18:26:39
[quote=tha_watcha;67814]Service Stack is added via Nuget. So you only need to recompile or do a Nuget Package restore.[/quote] Even after doing a Nuget restore, this is what the solution looks like (after I manually add the YAFNET source folder to the proper directory path expected by the solution file). http://screencast.com/t/kMH1uqgvU6kA

Posted by: tha_watcha - Friday, 16 December 2016 18:46:56
[quote=hismightiness;67818][quote=tha_watcha;67814]Service Stack is added via Nuget. So you only need to recompile or do a Nuget Package restore.[/quote] Even after doing a Nuget restore, this is what the solution looks like (after I manually add the YAFNET source folder to the proper directory path expected by the solution file). http://screencast.com/t/kMH1uqgvU6kA[/quote] Sorry i forgot to remove the projects from the ormlite vs solution file. I updated the repository.

Posted by: hismightiness - Friday, 16 December 2016 22:22:08
Unfortunately, while that fixed one issue, it exposed new ones. Now, the missing projects are no longer required, but I can't build because of missing references, and I can't update Nuget due to .NET version conflicts. I tried building and rebuilding from the solution level, as well as the module and YAF levels. All have the same results. When I attempt to build, these are the first few messages in the output that end up cascading build issues: [indent]1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "ServiceStack.Common, Version=4.0.0.0, Culture=neutral, PublicKeyToken=e06fbc6124f57c43, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. 1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "ServiceStack.Interfaces, Version=4.0.0.0, Culture=neutral, PublicKeyToken=e06fbc6124f57c43, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. 1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "ServiceStack.OrmLite, Version=4.0.0.0, Culture=neutral, PublicKeyToken=e06fbc6124f57c43, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. 1>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "ServiceStack.Text, Version=4.0.0.0, Culture=neutral, PublicKeyToken=e06fbc6124f57c43, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.[/indent] So I attempt to update the solution using nuget, and I see that there are 4 updates: http://screencast.com/t/mrqfZJCh57q This is a warning message shown when attempting to update using the nuget package manager: http://screencast.com/t/9zqICsqDlz This is the error message and log from attempting the nuget update: [indent]Attempting to gather dependency information for multiple packages with respect to project 'YAF_source\YAF.Core', targeting '.NETFramework,Version=v4.5.2' Gathering dependency information took 507.94 ms Attempting to resolve dependencies for multiple packages. One or more unresolved package dependency constraints detected in the existing packages.config file. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'Farsi.Library 2.5.1.5', 'valueinjecter 2.3.3' Resolving dependency information took 0 ms Resolving actions install multiple packages Attempting to gather dependency information for multiple packages with respect to project 'YAF_source\YAF', targeting '.NETFramework,Version=v4.5.2' Gathering dependency information took 648 ms Attempting to resolve dependencies for multiple packages. One or more unresolved package dependency constraints detected in the existing packages.config file. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'Farsi.Library 2.5.1.5', 'jQuery.FileUpload 9.12.3', 'jQuery.UI.Combined 1.12.0' Resolving dependency information took 0 ms Resolving actions install multiple packages Retrieving package 'Farsi.Library 2.6.0' from 'nuget.org'. GET https://www.nuget.org/api/v2/Packages(Id='ValueInjecter',Version='3.1.1.3') GET https://www.nuget.org/api/v2/Packages(Id='Farsi.Library',Version='2.6.0') Retrieving package 'ValueInjecter 3.1.1.3' from 'nuget.org'. Removed package 'valueinjecter 2.3.3' from 'packages.config' OK https://www.nuget.org/api/v2/Packages(Id='ValueInjecter',Version='3.1.1.3') 96ms OK https://www.nuget.org/api/v2/Packages(Id='Farsi.Library',Version='2.6.0') 99ms Successfully uninstalled 'valueinjecter 2.3.3' from YAF.Core Removed package 'Farsi.Library 2.5.1.5' from 'packages.config' Successfully uninstalled 'Farsi.Library 2.5.1.5' from YAF.Core Install failed. Rolling back... Package 'Farsi.Library 2.6.0' does not exist in project 'YAF.Core' Package 'Farsi.Library 2.5.1.5' already exists in folder 'C:\Websites\yafdev\yaf_dnn\packages' Added package 'Farsi.Library 2.5.1.5' to 'packages.config' Package 'valueinjecter 2.3.3' already exists in folder 'C:\Websites\yafdev\yaf_dnn\packages' Added package 'valueinjecter 2.3.3' to 'packages.config' Package 'Farsi.Library 2.6.0' does not exist in folder 'C:\Websites\yafdev\yaf_dnn\packages' Executing nuget actions took 2.22 sec Could not install package 'Farsi.Library 2.6.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author. ========== Finished ========== Time Elapsed: 00:00:06.8807025[/indent] Could it be possible that the solution is missing other updates that should be committed? I don't know if you think it will help, but you might want to create this environment from an empty folder again yourself to see what I'm running into.

Posted by: tha_watcha - Sunday, 18 December 2016 11:23:32
Yes looks like the folder structure with nuget is a bit problematic, with source of the packages folder. Also Update all the new nuget packages is also a bad idea. The easiest solution is to opnen & compile the YetAnotherForum.NET.sln solution first and next you can compile the dnn solution

Posted by: hismightiness - Wednesday, 21 December 2016 22:30:21
When I began figuring out how to get this solution up and running, I found out that I needed to have the following folder structure, just to have the DNN solution open properly. http://screencast.com/t/NBphR4g6kj Unfortunately, when I open the YAFNET solution, I can try to build, but I get all kinds of missing assembly errors (very similar to above). It doesn't matter if I clean or not, or whether I choose to build or rebuild. Something is wrong with this project structure or something. Do you have clear instructions on how a new person can setup a fresh (brand new) development environment for helping to build the DNN YAF project?

Posted by: hismightiness - Wednesday, 21 December 2016 22:34:20
Some other usefful information I was thinking about... My development environment is VS 2015, and I pulled the latest source from both DNNYAF and YAFNET, which is what you see in those folders in the link above. I don't know if the DNN project was supposed to use a specific branch and/or commit/tag.

Posted by: tha_watcha - Thursday, 22 December 2016 10:01:49
[quote=hismightiness;67834]When I began figuring out how to get this solution up and running, I found out that I needed to have the following folder structure, just to have the DNN solution open properly. http://screencast.com/t/NBphR4g6kj Unfortunately, when I open the YAFNET solution, I can try to build, but I get all kinds of missing assembly errors (very similar to above). It doesn't matter if I clean or not, or whether I choose to build or rebuild. Something is wrong with this project structure or something. Do you have clear instructions on how a new person can setup a fresh (brand new) development environment for helping to build the DNN YAF project?[/quote] Sorry but i can not reproduce this you are the first person with the problem. I downloaded the Master branch of YAFNET as zip, extracted all files in to a folder for example C:\YAFNET\ and open the solution in VS 2015 and compile the solution.

Posted by: hismightiness - Thursday, 22 December 2016 18:58:55
What were the exact steps you took to reproduce a working DNN YAF development environment? Here's what I did: - Clone the DNN YAF project locally to C:\dev\yafdev\yaf_dnn\ (this step needs to be first because of how git clones a repo) - Add the YAFNET folder and files to C:\dev\yafdev\yafsrc\ - Try to build either solution I get the errors. Did you do something more or different?

Posted by: hismightiness - Thursday, 22 December 2016 19:29:07
Odd... I just cleared out everything and started from an empty folder (again). This time, I'm able to build both, in the order I previously stated. I'll begin figuring out the packaging and how to make my required changes next. Thanks for helping!