I am having some trouble upgrading my dnn 7 website. I am upgrading from 7.0.5 to 7.0.6 and I have previously tried upgrading to 7.1.0 but I ran into errors, now I have left over files from the previous upgrades left in the instal/authSystem install/provider install/module folders.
Can I empty these folders before copying over the upgrade package over the current version? Should they be empty? or how can I figure out what the default contents should be for the install folder when upgrading.
As to your question, simply empty the INSTALL folder and get the INSTALL folder from the upgrade package.
Really though, you should take your backup from before you attempted the upgrade, and take all of the files from that backup, and start with those, essentially starting with a clean folder, copy the files into that folder from the backup, then perform the upgrade.
Related
I have a nuget.config file in root folder of my solution, I want to use repositoryPath, instead of globalPackagesFolder, as globalPackagesFolder downloads a very long list of packages to folder, but repositoryPath does not work instead, which really confused me.
<config>
<add key="globalPackagesFolder" value="./packages1" />
<add key="repositoryPath" value="./packages2" />
</config>
I will only keep 1 line for packages folder. everytime when I made changes to nuget.config, I've run git clean -xdf and also restart Visual Studio 2019.
That's not possible.
Which folder is used is a function of the project style.
From the managing the global packages and cache folders doc.
The global-packages folder is where NuGet installs any downloaded package. Each package is fully expanded into a subfolder that matches the package identifier and version number. Projects using the PackageReference format always use packages directly from this folder. When using the packages.config, packages are installed to the global-packages folder, then copied into the project's packages folder.
The global packages folder can be shared across projects, solutions and even a whole machine.
If you have PackageReference projects, you have no choice but to use the globalPackagesFolder. Note that you can't have them point to the same location, because as you have observed, they have a different structure.
Currently my application is running on Evoq Content 7.3 and I was trying to upgrade it to Evoq Basic 8.5. I have copied the upgraded file into my application directory And now when I try to access the http://MYWEBSITE/install/install.aspx?mode=upgrade , It is giving error "resource can not found Requested URL: /install/install.aspx.
Please advise.
This looks like some files were removed from the install directory, probably as part of a security precaution. I'm not sure why they were not added back with the upgrade package.
You might be able to fix this by copying the install directory from an appropriate install package. Just the install directory.
As always, make a copy of your database and complete file directory first, just in the event that what you do fails.
I need a way to figure out which files are left over after upgrading Moodle to a newer version.
I have:
Old version + many plugins
New version
Merged version
In the new version some files have been removed but they still exist in the merged version.
I could start with the new version and copy all the plugins but many are in different sub folders which will take too long.
Is there a quick way to list or delete these left over files?
I would create a clone of Moodle in a separate folder.
git clone git://git.moodle.org/moodle.git moodleclone
Then check the version of Moodle in /version.php in your code - look for $release = '2.x.x. Then checkout the exact version of the Moodle clone
cd moodleclone
git checkout v2.x.x
Then use Meld to compare the 2 folders. http://meldmerge.org/
meld ../moodleclone ../yourmoodleversion
This will then show any code differences between the 2. You can see if its an official Moodle plugin or one that has been added.
It would be better if you use the uninstall plugin option via site admin -> plugins because it should remove any data in your database too. You might also want to do a clean install in a new database using the Moodle clone, then dump and compare the database structure from the clone and your code to see if there are any database changes.
I am trying to upgrade my DNN version from DNN 7.2 to DNN 7.4.
But it just keep processing.
Do you have Microsoft AJAX and AjaxControlToolkit DLLs in the BIN folder of your website?
If so, try removing those and see if the process will work. (you can put them back in after the upgrade)
You may have some old install files in your /install/module folder. Before you start upgrade, remove all files from that folder except placeholder.txt.
I installed SQLite into my WPF project via Nuget. Then added the entire project to a remote repo. Then I cloned the project on another machine, and had a broken build.
x64\SQLite.Interop.dll was missing.
I'm puzzled why Git didn't include one file from my project. I checked the repo on BitBucket and confirmed it is not there. Git status reports nothing to commit, working directory clean
It added the x86 version, but not the x64 version, I can't imagine why.
(project)\x64\SQLite.Interop.dll Git ignored this file!
(project)\x86\SQLite.Interop.dll
You might want to check the .gitignore file at the root of the repo. If it contains for example x64, it would ignore this file.
There would be two main possibilities then:
edit this file to fit your need
or force this file to be added; ie: git add -f x64/SQLite.Interop.dll
However, committing binary files is often frowned upon. It's true in particular if you want to keep up to date with the latest package, hence if you plan to commit new versions of the dlls on a regular basis.
You might rather want to consider Nuget package restore feature. Basically the idea is that you commit a config file, and the client will automatically download the corresponding packages.