I am porting a web app to Windows 8.1.
In doing so, I run into Error APPHOST9626, This reference causes failures when used outside of the debugging environment.
After researching, the reason this occurs is because the folder for some of my resources is named "ko" which the application builder misinterprets as being the korean language folder.
One solution is to rename the ko folder, but I would also have to rename all references to said ko folder and it would be a pain.
Is there any way to disable the ko folder being interpreted as the korean language folder?
This what is found in this sides....it works for me !
Hi, Issue is solved after removing all language folders from "\Program
Files\Microsoft SDKs\Expression\Blend.NETFramework\v4.0\Libraries".
Thanks a lot :)
-- Happiness is only real when shared :)
Related
Where should I keep my projects? There is no special folder in VS Code. Do I have to create it? Where? Maybe .vscode folder is the best option? Or this will be automatically removed after you uninstall/reinstall the editor?
You can keep them in the default location:
%USERPROFILE%\sourcerepos
Or create another folder and name it Projects (for example) in another drive.
Any folder can be your project. That’s why there’s the “Open folder” command. How to best organize your project inside that folder depends on what type of project it is.
So I have a web application in Visual Studio 2010. Im depending on 2 DLLs. One of these are not a "real" DLL but a COM object. The first DLL is wrapper for this COM object.
So the first DLL is easy to add with a reference and when I deploy it gets put in the bin folder on the destination. The problem is the COM DLL. I can not add it as a reference. So I tried the accepted answer on this How do you include additional files using VS2010 web deployment packages? but I could not make it work. (some comment suggest this edit should be in the .pubxml file but i don´t even have that one?)
I also tried the second answer on the same question but still no luck.
The only thing that works if I go to the project properties and select "all files in this project" but I really don´t like that.
I know these answers I refer to are a bit old so maybe there is a new way of doing this?
I have experienced a similar situation in the past. The only viable way around I have found was to manually copy the files I needed when building the application using the "Build Events" screen (Go to "My Project" > "Compile". It is a the bottom right hand corner).
In the "Post-build event command line", I have entered a script that copies the DLLs I need into the bin folder of my web app:
XCOPY "E:\ThirdParty\Example.dll" "$(TargetDir)" /Y /R
This script simply copies the dll "Example.dll" from a repository folder into the bin folder of the web app I am compiling. You can find a lot more about these build events on MSDN: https://msdn.microsoft.com/en-us/library/ms165412.aspx
Hope this solves your problem and good luck!
I managed to work it out. I found this http://sedodream.com/2012/06/15/VisualStudio2010WebPublishUpdates.aspx page and installed the update for web publishing.
After that I had the pubxml files and I edited it according to the guidelines.
As found on http://www.asp.net/mvc/overview/deployment/visual-studio-web-deployment/deploying-extra-files
I am running an Italian version of Windows 7.
Some folders, such as C:\Users, appear as C:\Users
when I run cmd and do an ls from the C: directory.
However, when I use Windows Explorer, this Users
folder shows up as Utenti. Also, when an
install script installs to C:\Users and I
go to Windows Explorer, I can click on
C:\Utenti and still view the stuff.
Can anyone explain where this
translation is configured and how
it works at a deeper level, as this
happens with most folders on the
system which seemingly end up
having two names in the Italian version of Window 7?
Thank you for any pointers or
more in-depth information
concerning the peculiarities
of such mechanism.
The localized folders are actually symbolic links to their english counter parts. The original english folders are hidden system files. This way the user only sees the folders in their language but they are still accessible under their english names. This is a big plus of Windows Vista/7 because before if a script accessed C:\Program Files it was not usable under non-english versions of Windows.
You can show the hidden original english folders if you go to tools -> folder options -> show system files (or something similiar, out of my head).
As Felix Dombek mentioned in his comment, this is due to the desktop.ini, which can be found in your Users folder (and other folders as well).
This file is used by the File Explorer and the Shell to customize the appearance of folders.
The LocalizedResourceName entry is responsible for the displayed foldername, which is used to determine the correct DLL and the stringID, the foldername should be loaded from.
I am developing a package using Installshield 2008 Primer Edition and Project type is Installscript MSI project.
The problem I am facing is during installation I am installing some of the files to the following location C:\Program Files\Company\SystemFiles from this location I am copying and adding the set of files into System32 folder, it contains DLLs and OCX files, copying into the System32 folder has been done using Installscript.
Due to this during uninstallation, the installed file is getting removed from System32 due to this other dependent application which requires the same set of DLLs have stopped working.
I have approached Installscript to copy files from ProgramFiles to System32 Folder rather than using built-in options because we have an issue during the upgrade in order to avoid that I am using Installscript.
Even I have tried several workarounds like setting the file attributes after file copies to System32 using Installscript like FILE_ATTR_SYSTEM which sets the system attribute but still files are getting removed during uninstallation.
Any idea how to give file attributes as PERMANENT or SHARED; will this help, and if it will, then how can I set it using Installscript?
I have 2 ideas
1)I think you can use SHARED option as this wont remove the files while uninstallation.
2)Also when i was facing similar issue , what i did was putting all the required files in the installation directory itself so that while uninstalling only the installed files will be removed.(I know this is not a best solution)
(NOTE:I have worked on Install shield some 6 years back and so remember only certain things)
You can also disable logging from Install Script. This will make the installer "forget" that it installed specific files groups or features.
You should make sure to enable logging once again after you have copied the files that you want to permanently leave on the system.
If you don't remember to enable logging after you have disabled it, your uninstall process may not work correctly.
Syntax is as follows:
Disable(LOGGING);
//Add code to copy your permanent files here
Enable(LOGGING);
For InstallScript projects:
To prevent the files in a particular Component from being removed during uninstall:
1-Select the Components view from within the Organization folder.
2-Select the component that contains the files you do not wish to remove during uninstall.
3-Change the "Uninstall" property in the right pane to a value of "No."
For MSI Projects:
To prevent the files in a particular Component from being removed during uninstall:
1-Select the Components view from within the Organization folder.
2-Select the component that contains the files you do not wish to remove during uninstall.
3-Change the "Permanent" property in the right pane to a value of "Yes".
I see this is an old question but I just came across this. Seems to be a common problem. One good solution is to stage the files to a private directory mostly program files and then have a custom action do the copy and register (ocx etc). Installshield remembers what it copied so it tends to remove them. Do not disturb anything else like logging (my recommendation). Set conditions on the custom action so that it doesn't run during Uninstall.
Although sometime back I did another weird implementation which only programmers are used to doing.. Packed the files as resources and created my own code to extract and deploy (Something that Process Explorer kind of tool does). There were certain use cases that warranted this kind of implementation. But again this is complicated and obviously reinventing the wheel. Unless you are good with C/C++ and Windows API this would be difficult. I would still suggest you stay away from this kind of implementation because it is also considered a "virulent behavior". Yet, so far I never got warnings from the Anti-malware products.
How to run the exe file to other system?
Using VB 6
I copied the exe file to other system, then run that exe file, it not working it showing error
“component comdlg32.ocx or one its dependencies not correctly registered a file is missing or invalid”`
Can any one help me how to avoid this error?
When deploying VB6 applications, you should create a Setup, this will manage the DLL's that the VB6 application depends on. Since it is not enough to just copy the .Exe and .Dll's. You also need to register them.
The creation of the setup is included in the VB6 environment.
You can read this http://support.microsoft.com/kb/830761 which is very comprehensive.
1: http://support.microsoft.com/kb/830761 for more information.
Or if you just want the redistributable files check this kb http://support.microsoft.com/kb/290887
Copy and register the comdlg32.ocx on other system. Link: Fix Missing Comdlg32.ocx Run time Error in Portable apps.
Create an installer for your program.
Unless you are deploying your program to really old versions of Windows (prior to XP), one nice alternative is to create an XCopy package using reg-free COM. This is fairly easy for most simple programs using Make My Manifest though it can be done by hand or using other tools if you invest in a little study.
Even then a formal installer package is usually desireable though, if nothing else to create Start Menu shortcuts and set up application workspace directories.
Keep in mind that even the PDWizard is difficult to use blindly. Packaging and deployment is a topic that requires some learning investment.
Outdated or missing comdlg32.ocx runtime library is causing this error. Here is a copy of comdlg32.ocx (~60 Kb Zip). Download the file to the Desktop and extract the comdlg32.ocx to your the Windows\System32 folder.
Note: If you already have a copy of comdlg32.ocx, backup the existing file to a different folder and delete it from System32 folder.
1. Download comdlg32.zip and save to Desktop.
2. Unzip the file using WinZip or any other utility.
3. Extract comdlg32.ocx to Windows\System32 folder.
4. Type the following command from Start, Run dialog:
regsvr32 %Systemroot%\System32\comdlg32.ocx
Typically a VB 6 app will consist of an .exe some .dll libraries and a config.ini file. The exe is the starting place and it consumes the dll's and config.ini and other resources to run => you have to have all parts in the same directory for the app to run typically called "packaging" an app. E.g. An installer simply ensures that all those files in a packaged app are placed on a users computer in an Windows application directory, and creates a shortcut launch icon so that a user can click the shortcut in the start bar and the app will run.
To "package" your app (put the dll's and exe in the same folder) you can use an Add-In called "Package and Deployment Wizard":
And here is a demo of using it: https://www.youtube.com/watch?v=XT7jaoAiKDo
You can either package and create an installer and package or just create a package:
Now if the Deployment Wizard doesnt show as an add-in on your VB6 Editor Installation, go to editor's program folder and find the tools Tools folder, i.e:
Then you should be able to find the Deployment Wizard there:
Open it to use it.