I am upgrading an old N2CMS website to the newest version released in the trunk (2.2.5 or something like that), following these instructions https://github.com/n2cms/n2cms/blob/master/docs/releases/upgrade_2.2.1.txt but i am getting an error when tring to compile the project:
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Has anyone done this before and know if there's anything else i should be doing appart from just copying files?
Thanks
Complete text of this error contains the name of DLL you are missing. Read it carefully and you will find out what DLL you need to add. It could be something like Lucene.dll which was introduced recently (it depends how old your project is).
Related
As in the subject, we are currently stuck at very (!) old version 2.3.3.1. We must upgrade to the latest (or a least a much more recent) version.
I suspect I'll need a few steps to make such a version leap.
Please give me any pointers you may find useful. This has landed on me, and I've never worked with Artifactory before.
As you suspected, there are several versions you'll have to go through, like 3.9.x.
You can find more info here and here
Following the directions above:
I have taken us to 2.6.7 as a necessary upgrade step, and today I worked on moving to 3.9.2 as a next necessary step.
I have followed the official instructions from https://www.jfrog.com/confluence/display/RTF3X/Upgrading+Artifactory
The "empty" 3.9.2 worked fine of course, so I proceeded with the copy of the filestore and then the import of the System export. The Export had been done as instructed, i.e. with Content excluded, and nothing else excluded.
The import finished but with 99 errors. These were of these three types:
A file missing from the export. In all cases, the export contained a folder with the same name as the file but with a ".artifactory-metadata" appended to its name. So for example instead of
/BACKUP_DISK/ARTIFACTORY/20200402.192450/repositories/jboss-releases-cache/jboss/jboss-j2ee/4.2.0.GA/jboss-j2ee-4.2.0.GA.pom
...in the export there was this folder:
/BACKUP_DISK/ARTIFACTORY/20200402.192450/repositories/jboss-releases-cache/jboss/jboss-j2ee/4.2.0.GA/jboss-j2ee-4.2.0.GA.pom.artifactory-metadata/
...containing two files, artifactory-file.xml and artifactory.stats.xml
Errors about failure to import a file because "MD5 value 'null' is not a valid checksum"
Errors about failure to import file because " Artifact rejected: The repository 'codehaus-cache' is blacked out and cannot serve artifact"
The last disturbing thing is that the new installation in the Home page states that there are half as many artifacts as in the 2.6.7 installation. I wonder if some kind of merging/relabelling has been done, and I should not worry about that.
I'd be grateful for any clues on the above.
Cloning a project and it looks like it comes down fine, until I look in the references and they all have the yellow warning triangle. Then my Error List shows all the references as Warnings. My application is on Visual Studio 2017 and it is MVC with C# coding using .NET Framework 4.7.2. In my normal application, original, the references are perfectly fine and no errors and it works great. Builds and works fine. Once I bring down the clone is then the references are lost. I've done a build on the cloned version and it shows all the references as warnings.
I've double clicked a reference and received an error popup box of "This project cannot be viewed in the object browser because it is unavailable or not yet built. Please ensure that the project is available and built". It feels like Azuredev-ops is just missing my references and their location. I am the only one working on this, so there should be no conflicts. I've posted and cloned right after posting, with same result. My code and Web configs look just fine. I have cloned on other people's system too, and same problem with this application. FYI, many of my other applications are working fine using the clone. Just 1 application is having issues. My references are separated in that some are Copy Local True while others are False. I've also removed a reference and added it back, and it comes back with a warning as if it were never added.
Warning message for individual reference:
The referenced component 'EntityFramework' could not be found.
I am also seeing errors for NuGet packages not being there, but when I look I see the package folder with all it's components in it.
It says that for all my windows core references. And just warning symbols in my reference folder for other references.
I am expecting no errors when I bring down the clone. I've upload using my machine and cloning should be able to use the same reference locations. It just feels like AzureDev-Ops is stripping my reference links out, and then going I can't find them.
Azure-DevOps clone shows references as warnings
To resolve this issue, you should make sure of the following:
Make sure you have checked those two options Allow NuGet to download missing packages and Automatically check for missing packages during build in Visual Studio:
Make sure you do not check the \packages folder to the source control.
When you clone the project from Azure-DevOps server and get missing reference error, you should use the NuGet command line Update-Package -reinstall in the Package Manager Console to force reinstall the package references into project. Check this thread for some more info.
Note: Especially need to pay attention to the third point.
Update:
Error:Mircrosoft.CodeDom.Providers.DotNetCompilerPlatform.2.0.0
According to the error message, it seems you are not add your packages to your packages source in Visual Studio.
You should publish your custom packages to the nuget feed or you can create you local nuget feed, then add the nuget feed path or local feed path to the package source:
Check this document for some more details.
Hope this helps.
I figured it out. I went to my original and did the Update-Package -reinstall. It came back with the Microsoft.CodeDom.Providers.DotNetCompiler.Platform.2.0.0 not there, but it added one, just not 2.0.0. Then I ran an uninstall of the Microsoft.CodeDom.Providers.DotNetCompiler removing it from my system. Then I posted my original up to AzureDev-ops. My clone came down, not all the references were messed up, some were still, but I did a rebuild and that cleared it up. Thank you to the responses, it pointed me in the right direction.
i'm having some issues getting modules to work on my app - I keep on getting told that the requested module cannot be found.
It is entirely possible that i'm not installing the modules correctly - so, for the purposes of this question:
Once i've downloaded the zip file from git hub using the green "download" button, what do i do to import the module into my project? Not how do i tell tiapp.xml to use the module - just what do i do to install it?
Can you please run through using the facebook module found at https://github.com/appcelerator-modules/ti.facebook
thanks!
Inside the zip file of the download you'll see there is a folder called modules. This is the same folder that is in your root of the project.
So, an iOS module should be installed in the /modules/iphone folder. Once added, you can add Facebook to your app like this:
<module platform="iphone">facebook</module>
If you want to specify a version you can do so like this:
<module platform="iphone" version="1.1.0>facebook</module>
note: I made up the version number
You can also add it through the tiapp editor in Appcelerator studio, although it doesn't always seem to find the module. This might be a bug in studio though, usually it works great.
HMMMM
Two main issues here, one directly relating, the other less so.
Issue 1
The link i gave to get the codebase from github is wrong - well, it gets the codebase, but not in a form that can be used as a module. It is, in fact, the uncompiled version.
Versions for download can be found here.
So that takes care of issue one, what about
Issue 2
The latest version for use is a bit broken. Seems someone (from the appcelerator team???) decided to make the latest 6.0.1 release have a minsdk of the (at this time) as-yet-unreleased version 6.0.0, and sets the apiversion to 3.
This breaks the current release of 5.5.1, so for anyone reading this prior to 6.0.0 for appcelerator, you will want to use this release version.
I downloaded the orchard galley server from codeplex repository in this link:
https://galleryserver.codeplex.com
when I want to run ClickToBuild.bat file according of the Readme.txt file for build and run all of the tests in both projects, show this error:
any one can help me?!
thanks a lot
First of all, the project has been discontinued. So you probably will not have support from the author. second, its from 2011.
Looking at your errors, it might seem you are missing assets being referenced. If you look closely to the project tree and read the Error you will see how there are Nuget packages being used. those might need updating for your project to build.
If it is an old nuget version, depending on your VS version might have problems but it salvageable. Just need to make sure all your packages are updated before building.
If you look at UpdateNuGet.bat you will be able to see how it tries to do something in the folder where the compiler tries to find the asset.
Good luck
I found Autofac AggregateService awesome but what is the right way to include it in my project: clone it from code.google.com or use NuGet?
I got used to use NuGet but I can't find nothing about AggegateService there. Any help?
It seems that AggregateService and the other Extras are currently "in limbo". There's been a recent change in that the contributions are now being made part of the same solution as Autofac core, while they were previously a separate solution. From the current build file you can see that extras will be made available as a separate Autofac.Extras package and a separate download from the Autofac page.
Meanwhile, you can use AutofacContrib 2.6.1 or to grab the source and compile a dll yourself.
Btw, thanks for finding AggregateService awesome ;)
Update: actually, reading the build file properly (and looking at the current source structure), the Extras parts will be distributed as individual packages. So expect to find Autofac.Extras.AggregateService on Nuget in the future.