Kentico | Upgrade tool fails to find website sln file - kentico

I am having difficulty using the upgrade tool for my website which is version 7.0.5354.21135 in my attempts to upgrade to version 10.
I ran the Kentico Upgrade\CodeUpgrade100\Tool>CodeUpgrade.exe file on my sln project file but it returned the following error 'Solution file not found'. I have changed the file structure of my project and the name and location of the CMS folder which might be the cause? (I directed cmd prompt to new file name/location i.e. not the inetpub/wwwroot folder)
I also tried to reinstall Kentico 7 and its 7.0.53 Hotfix in an attempt to upgrade a fresh install but my installation failed.
I am trying to upgrade my local development site from 7.0.5354.21135 up to 10 to test if any issues would result in such an upgrade (plan to do so in near future with live site).
UPDATE:
I moved files back to original inetpub folder and renamed sln project to 'WebProject.sln' but am still seeing the following error:
This is a newly created sln project file from original site files in VS13. Do I have to alter something else to get this new sln project file to work?
Thx

For v7 if you made changes to your solution as a whole meaning, moving your .sln file outside of the root of the website, you will need to modify your solution to place it back in there. Also make sure your .sln file is either named "WebProject.sln" or "WebApp.sln"

Solution was to download a fresh version7 install, copy across my local dev site files, open in VS and resave WebProject.sln or equivalent project. Then I built project and refactored through various redundant member objects removed from version 8

Related

Installshield Project upgrade product name , registry, install directory

I am using Installshield 2014. I want to upgrade and rename my project name, registry, installation directory. I have updated these all information and generated single Image setup file. but my installer is not upgrading successfully.
I am getting error as "Error 1316 : can't read files from temp folder".
Error desc :
My older installer product name is x.msi
new installer product name is y.msi
but when i am upgrading x.msi to y.msi it is searching x.msi in c:\users\AppData\local\Temp\2{xxxxxxx}\x.msi.
I have verified in above location y.msi file is available but installer is trying to read older x.msi file only.
please help me to resolve this issu.
When you change the name of your .msi file and create a minor upgrade, you may encounter a 1316 error. Either rename y.msi such that it matches x.msi, or create a major upgrade instead of a minor upgrade.

Need Help Uninstalling Stencyl

When I try to install openFL with Haxe I get this error:
C:\Users\Dude>haxelib install openfl
You already have openfl version 3.3.0 installed
[file_contents,C:\Program Files (x86)\Stencyl\plaf\haxe\lib/openfl/.current]
I have uninstalled Stencyl from program files (Win8.1_64bit) and ran CCleaner to make sure I was wiped out. Also I checked system and user environmental variables but didn't found Stencyl anywhere.
Then I have reinstalled Haxe over again, but for some reason I keep getting the same error.
After the fresh installation, I have checked the installation location of Haxe by using the >haxelib config command but still I get this weird output
C:\Users\Dude>haxelib config
C:\Program Files (x86)\Stencyl\plaf\haxe\lib/
Currently haxe is installed at C:\HaxeToolkit on my machine
Well I just entered the Stencyl keyword in the windows search bar and saw this file: .hxcpp_config.xml. This file and another one called .haxelib was located in my user Home folder.
The problem was fixed after deleting both of this files.
Also I found were stencyl was hiding (ಠ_ಠ ). The file .hxcpp_config.xml directs to the AppData folder in the user directory (C:\Users\Dude\AppData\Roaming\Stencyl)

Installshield LE is not updating the files while attempting upgrade

I've spent literally the last 5 hours around this, and can't get it to work.
I've done everything it's said in similar questions.
Change the ProductCode, keep the old UpgradeCode, Change product version.
Again and again. It doesn't replace the updated .exe file it's supposed to.
What am I missing?
Edit: I also have doublechecked the .exe build in visual studio, there it's builded and working properly. Only when I run the setup that's supposed to copy it to install folder, and only then it fails, keeping the old .exe file there, and not updating.
Does the exe on the target system have the same or higher file version than the exe you are installing? Windows installer will not overwrite a file that has a higher file version then the file it is installing.
look at the install log. search for the component name, check the Request/Action state. Is the state set to "Local"? Also search for the file name to see if msiexec tried to copy it.

Installing Emacs Emulation keybindings -- Invalid VSIX package

I'm trying to install the extension for Visual Studio 2012 that allows emacs key-bindings.
I'm following through the steps here:
Emacs Keybindings in Visual Studio 2012 or 2013
I'm up to step 5:
Run the vsik file as administrator. This is required so the extension
can write Emacs.vsk into the program files folder. I wasn't sure the
best way to do this so I ran a command prompt as admin and then
executed start emacsemulations.vsik from the prompt.
So, running emacsemulations.vsix from an administrator command prompt,
I get the following error "This VSIX package is invalid because it does not contain the file extension.vsixmanifest at the root."
I'm not changing any of the file names inside the package.
I'm thinking this may have something to do with how windows zips up the file -- I'm able to recreate the problem simply by unzipping and rezipping the EmacsEmulation.vsix file without changing the contents of the vsix package.
If anyone has any suggestions on how to fix, or even better, the actual updated vsix file itself, I'd be very grateful!
The issue you have relies on the way you are zipping your file, what you should do is zip all files inside the folder you created (in this case, "EmacsEmulations") when you unzipped it.
Step into the EmacsEmulations folder.
Select all files.
Add to .zip
Rename the .zip output to EmacsEmulations.vsix
I'm trying to get this extension to work too, so good luck!

Why is Nuget trying to access my SVN files?

I'm trying to update the Nuget packages in a solution I have, but this is what it does for all of them when I try to update
Successfully installed 'knockoutjs 2.2.1'.
Updating 'knockoutjs' from version '2.2.0' to '2.2.1' in project 'MyProject'.
Directory 'Scripts\.svn\text-base' is not empty. Skipping...
Directory 'Scripts\.svn' is not empty. Skipping...
Successfully removed 'knockoutjs 2.2.0' from MyProject.
Successfully added 'knockoutjs 2.2.1' to MyProject.
Access to the path '(solution path)\packages\knockoutjs.2.2.0\Content\Scripts\.svn\text-base\knockout-2.2.0.debug.js.svn-base' is denied.
Access to the path '(solution path)\packages\knockoutjs.2.2.0\Content\Scripts\.svn\text-base\knockout-2.2.0.js.svn-base' is denied.
Access to the path '(solution path)\packages\knockoutjs.2.2.0\Content\Scripts\.svn\all-wcprops' is denied.
Access to the path '(solution path)\packages\knockoutjs.2.2.0\Content\Scripts\.svn\dir-prop-base' is denied.
...
It pretty much does that for every SVN file. Then says it wasn't properly uninstalled and I need to restart Visual Studio for the changes to take effect, but that doesn't solve anything. I have to manually clear out the files and remove the .deleteme file that gets created.
I also tried running Visual Studio 2012 as Administrator but that didn't change anything. I also have full permissions on my Windows 7 machine to the entire project.
I thought .svn folders were supposed to be ignored by Nuget? Is it trying to delete the older package folder? I'm fine with it taking out all the content files, as long as it leaves the .svn folder alone. I can always mark the files as deleted on the next commit.
Also, I know I can run Nuget without commiting the packages to source control, but I don't want to do that. The feature isn't enabled and the checkbox that lets Nuget download missing packages is not checked. So if it thinks that source control integration is disabled I don't know why.

Resources