Environment variables and other features are missing in InstallShield project - installshield

I have existing .ism project (InstallShield 2018R2 Professional), which contains full list of features, the project window looks like this:
When I create a new project, selecting InstallScript type, the same project window is missing many features:
Currently I am looking for Environment Variables window, but many other features are missing as well. How to get all these features enabled in the project?
It looks like my InstallShield edition supports them, since existing project looks OK. But I cannot create a new project with the same functionality.

Your existing project could be basic MSI or installscript MSI project which is different than your new project with installscript project type.

Related

Visual Studio 2022 - File Add New Item CSS, HTML, JS missing

I have 2019 Web Project I'm trying to open in Visual Studio 2022 and it's missing a lot of common file types, HTML, CSS, JS and Text to name a few. If I open the project by going to File -> Open -> Folder the expected file types are available but the Azure Dev Ops integration doesn't work.
Any pointers on how to get this working. Someone recommended building the New Item file templates but that seems like a chore for such a simple set of file types.
Update: If I change the Solution Explorer view to Folder View then I can add the files I expect, but with Folder View I can't check-in or publish. I will need to toggle between Solution View & Folder View complete those actions. To clarify further, how/what populates the Solution Explorer(Solution View) -> Add New Item menu?
In Visual Studio 2022, the .NET Framework project and item templates are now optional components. At the time of installing VS 2022, you need to manually check this option on the ASP.NET and web development section. If somehow this got missed during the installation, you can enable it by following the below steps:-
Open Visual Studio Installer
Click on Modify
Expand Asp.Net and web development
Check .Net Framework project and item templates
Screenshot:-
The above steps will bring back the missing HTML, CSS, JS, and other templates
One of the workaround you can follow to resolve the above issue,
We are trying the same with console application and trying to add html and can able to get it as well using VS-2022 with version 17.2.6.
Make sure that you have open the correct project in your environment.
HERE ARE THE SCREENSHOT FOR REFERENCE:-
Alternatively if you want to add an item template to the Add New Item dialog box in visual studio please refer this MICROSOFT DOCUMENTATION| How to Create item templates
For more information please refer the below links:-
SIMILAR SO THREAD|Can't find ADO.net Entity Data Model template in VS2017 .
This is a pain. It happened to me with the last upgrade. To fix it, open the installer, select "Web and Cloud", then "ASP.NET and web development." Check all the boxes through Intellicode, and then check ".Net Framework project and item templates".

Using Visual Studio 2015 for existing node-js client-side web projects

I have a team working on a client-side node.js application. The sources are stored in a source control. I'd like to modify and debug this application in Visual Studio 2015. They use other IDEs, and I would not like to add additional VS-specific files such as .sln to source control.
I'm able to clone the repository, create a separate empty solution and add the repository as an "Existing Web Site". However, Visual Studio do not recognize package.json, and do not install dependencies as it would for MVC6 projects. Consequently gruntfile.js would not work either.
Is there any way to make Visual Studio see and process package.json, or I'm on a wrong track here?
Instead of using the "Existing Web Site" option, create a new solution and add items to it. Web Site Projects types are a different, legacy project type.

VS Package Extension to add a new project type to the new projects options window

I woulkd like to create a Visual Studio extension. I chose the Package option since the AddIn option will be deprecated from Visual Studio 2013 and above.
So i installed Visual Studio 2012, and Visual Studio SDK 2012, and created a new VS Package project.
Now, I want my package to enable the user to create a new type of project. i.e: I want to extend the right click->new project options to contain a new model of project, which will be a standard Visual C++ project, with some additional configurations, links, references and etc.
I googled a lot, but found nothing.
Does any of you have an idea about this target?
Thanks in advance!
I think the Visual Studio Template Schema Reference contains all information you need to create custom project templates; see: http://msdn.microsoft.com/en-us/library/xwkxbww4.aspx
You can derive a project template from an existing project, which might be the way to go, since it creates a valid template that only needs some customizing. A template export can be done by using the Export Template command found in the File menu.
The template wizard will create a ZIP file containing the template manifest and all referenced files; just extract the archive and customize it in the way you want it (add/remove files, change information like name and description in the manifest). Once you´ve your customized template, create a new VISX package project and add the template ZIP file to it (using Add Existing Item command).
The last step will be to add an Asset to the VISX manifest. Open the source.extension.vsixmanifest file in the VSIX designer, goto the Assets tab and click the New button; this will open a dialog to setup the asset... choose Microsoft.VisualStudio.ProjectTemplate as the type - and File on filesystem as the source. This will allow you to pick the previously added ZIP file. Build the package - and you´re done.

Context menu does not display "add transform" in console job when using slow cheetah

I assume this is a simple fix considering I don't see any other posts about others having this issue. I am using VS2012 and I added slowcheetah 2.5.10.3 to the project using the nuget package installer.
I have tried opening a new console application as well as a unit test project, but in both I am not able to "add transform" to my App.config. The option in the context menu doesn't exist...
You will need to install the SlowCheetah Visual Studio extension to get the additional menus in Visual Studio. The NuGet package only adds a .targets file to the solution which is useful for command line (build server) scenarios.

Visual Studio 2012 Windows service .vdproj project migration

I'm trying to move a solution I have over to Visual Studio 2012 and one of the project types is .vdproj.
According to this link this project type is not supported in Visual Studio 2012:
MSDN says they recommend that you use InstallShield Limited Edition for Visual Studio.
The problem is, when I open up my solution in VS2012 and try to add a new "Enable InstallShield Limited Edition" project to my solution, I get an error message saying:
Creating project 'test'...project creation failed.
Why might I not be able to add a project of this type to my solution?
If I make a new empty solution I can't make an InstallShield project it in either.
I'm going to try to download InstallShield limited edition and see if it does anything.
I tried out that InstallShield download, and it added two extra project types, but I'm unable to create either of them. I'm able to add normal website projects to my solutions just fine, but not deployment projects.
The installer was named the same, but this one prompted me to re-start. After re-starting I was able to add an InstallShield project, but it gets created in its own solution. So, it looks like now I have to figure out how to use it, and I'll be good to go.
It's looking like the limited edition doesn't have support to install Windows services.
This will probably be long and boring because there's lots of steps, but I'd like to write up how to move from a Windows service installer .vdproj to the new InstallShield LE that's available in Visual Studio 2012.
Step 1: Create a merge module (.msm)
Follow the steps of this guide.
Notes:
You will need to install WiX 3.6 and isWiX
The latest release of IsWiX doesn't enable the Tools menu item in Visual Studio 2012. Edit the file: C:\ProgramData\Microsoft\MSEnvShared\AddIns\IsWiXAddin.Addin (XML) and clone the HostApplication element and update 10.0 to 11.0.
In step #8 of the guide, it references a code tab. This has been moved to the XML Editor item in the bottom of the left menu
I left the MergeRedirectFolder empty for my installation
Here is my isWix files view:
After you're done with the guide you should have an empty .wxs file that looks something like this:
Using the Component XML element pulled from here you should end up with a .wxs file that looks like this:
Hit build and you should now have a .msm file.
Step 2: Adding merge module to InstallShield
Go though the wizard to setup the basic install information like company and version information.
Find the redistributables view in ISLE. Right click the list and select browse for module. After your module is found and added, right click the modules and select properties. Set the destination folder drop down to INSTALLDIR. I had to set mine to the lowest level folder I created for my install path, so you might have to experiment a bit.
Build Project, and test on virtual machine
Redistributables Screen
If you're getting errors about the path being too long you might need to change the release location to something close to the root.
Here's a list of all the build errors for reference.
Now you should be able to run your installer and have it install/start a Windows service. A lot more work than .MSI files, we got it to generate in Visual Studio 2010, but overall it was not too bad.
While there is no easy or truly supported solution for Visual Studio 2012, Visual Studio 2013 users can get an extension from Microsoft in the Visual Studio Gallery.
I found this post which says you must download InstallShield first. It's a very confusing way to work. I suggest to vote up the post on the connect site and give them comments letting know how poor that is. They could at least give a more descriptive error http://connect.microsoft.com/VisualStudio/feedback/details/732196/project-creation-failed-for-installshield-limited-edition#tabs

Resources