Is there any workaround to get Rational ClearCase running in VS2015 RC? It looks like no plugin is available yet. Can I somehow use the plugin from VS2013?
The solution proposed by user5337760 worked perfectly for me.
In ccvsisearchtoolwin_VS2013.reg and reg_VS2013.bat, globally change all the 12.0 instances to 14.0. (I don't use the Remote Client, so these 2 files are the only ones I needed.)
Check the environment variables in reg_VS2013.bat to be sure they match your setup.
Run reg_VS2013.bat.
According to http://www.almtoolbox.com/blog/installing-microsoft-visual-studio-2015-integration-with-clearcase, Microsoft Visual Studio 2015 is integrated with ClearCase as of release 8.0.1.10.
The same site has also a non-official Visual Studio integration with ClearCase 9.
First, apply the the latest fix pack for your ClearCase Client version. Support for VS2015 may already be included.
If not, start with the approach given by IBM for VS2013 http://www-01.ibm.com/support/docview.wss?uid=swg24036865
Before executing the scripts though, be sure to replace all references to VS2013 ("12.0") with ("14.0") in the batch and registry scripts provided.
Also, since you're probably using a 64-bit system, be sure to specify "Program Files (x86)" where appropriate.
Can I somehow use the plugin from VS2013?
You can try, but it isn't supported officially.
I don't know of a compatible ClearCase plugin for now.
Official support for Microsoft Visual Studio 2015 was introduced in ClearCase 8.0.1.10 as noted in the "What's New" page.
Related
From Prerequisites on the setup property pages, I selected the option to Download prerequisites from the component vendor's web site
There is no Windows Installer 4.5 in the prerequisites to install option..
because every im installing my setup using the sqlexpr_x64_ENU.exe in custom actions to install, run the setup after the extracting sqlserver it pops up the window says
There is a problem with this Windows Installer package. Aprogram run as part of the setup did not finnish as expected. Contact your support personnel or package vendor
im using VS2017 on windows 10
Exclude MSI Engine: You should not include Windows Installer 4.5 with any package these days. This runtime is from back in the day of Windows Vista - we are long since on version 5. Windows Installer should be deployed only via Windows Update as of today - in my opinion. Leave the runtime out of your setup.
No Concurrency: You can not run an MSI setup from within another MSI setup via a custom action. This is due to technical restrictions. There is a mutex set when an MSI runs its actual installation sequence, and triggering another installation sequence from within it will fail. A similar answer on the topic.
Setup.exe Launcher: What you need is to install your pre-requisites via a setup.exe launcher instead. This runs installations in serial, not in parallel. Which version of SQL Server are you installing? I see only a couple of versions available in the Visual Studio Installer Project launcher.
Other tools have features to allow you to install a setup.exe with embedded packages of various kinds in sequence. I have explained a myriad of times how to do this in previous answers. Here are just a few that I found quickly:
SQL Server named instance with Visual Studio 2017 Installer project (basically exactly the same issue - I suggest WiX the open source, free alternative)
Custom installer for application in Visual Studio 2017 (I suggest WiX and several commercial tools that are easier to use - maybe try to read this one)
Cannot call command.exe(SQL Server Setup.exe) while calling C# CA with parameters
How to create a MSI file which simply copies a directory to Program Files? (tools list)
Combine exe and msi file in one installer
Visual Studio 2017 Installer Project - include VC++ 2015 Redistributable
The general situation:
The problem is not Windows Installer 4.5, it's the fact that you are trying to do a recursive MSI install (the SQL one from inside yours) which is not allowed and will fail.
The MSI 4.5 engine is pretty much obsolete, about 10 years old, and anyway it's not the issue, and it's not clear why you believe it is. But it IS in the Prerequisite list on my VS 2017 setup project prerequisites - see 3 - even though you almost certainly don't need it.
There are some SQL Express options available in the Prerequisites of the VS setup project - right click the project in solution explorer and choose Properties, then Prerequisites.
I have my my setup project in (Visual Studio 2015: Community Edition) ready to be built and create my program installer. But, obviously the program will not work on other computers without the appropriate redistributable package installed on the clients computer.
So, I need to set that up in my project but I do not know how. I read in a post on another site that it is located in:
Project>>Setup Properties>>Prerequisites
But, all I just see are selectables for ".net framework" related things. Also, I read that merge modules are not good to use due to servicing issues.
If you have any insight into whether I am needing to download an extension for the correct prerequisite to appear, use merge modules, or something else it will be greatly appreciated!
I'm sure this is very simple but I can't seem to find an answer to this at the moment and my googling powers have returned nothing.
I previously had an issue with an Addin and SSMS gave me the option to disable it (which I took). I have since reinstalled the plugin but it still does not appear as I previously disabled it.
Does anyone know where I can find the 'Add-In Manager' in SSMS 2008 R2 like in Visual studio?
For 2008 versions of SSMS you have to check this registry key:
Key="HKLM\Software\Microsoft\Microsoft SQL Server\100\Tools\Shell\AddIns\"
You will find there 1 entry per installed add-in. Every add-in entry has setting:
"LoadBehavior". Set it to "1" to make SSMS load add-in at start-up.
You can check and see if your add-in is located in either of these directories:
%PROGRAMDATA%\Application Data\Microsoft\MSEnvShared\Addins\
%APPDATA%\Microsoft\MSEnvShared\Addins\
I believe disabling an add-in will simply remove/move it from one or the other of those directories, or possibly change the extension.
SSMS doesn't have any official support from MS for add-in functionality, unfortunately, so is lacking in tools to manage the add-ins. They have also stated that they won't support your installation of SSMS if you have extensions installed for it. Read here for more: http://connect.microsoft.com/SQLServer/feedback/details/265567/ssms-allow-support-for-addins-as-in-visual-studio
I have a Winform App that we uses internally that I publish through ClickOnce with SQL Express 2005. The app also references a couple of Microsoft.SqlServer dll's. I am trying to figure out how the Specific Version settings work. I have SQL 2008 installed on my machine they have 2005.
If I select Specific Version = false will it care that the users have SQL 2005 or does that depend on the dll.
Specifically, If I do not specify Specific Version does that mean it will just look in the GAC for any version of that dll?
"Specific Version" is only relevant when you compile, it has no effect at runtime. When set to False, the IDE won't complain when the [AssemblyVersion] of the reference assembly has changed. Which is not that great an idea, you ought to be aware of the changes you might have to make in your code because the assembly changed.
The CLR will not look for any version of an assembly in the GAC. Only a exact match is accepted. That's the default policy, you can override it with a <bindingRedirect> in the app's .config file.
Afaik, there isn't a provider for SQL Server that's specific to the SQL Server version number. Not quite sure about that.
Someone at MSFT who's related to the SQLExpress product told me today that it's so hard to figure out if it's installed already, they have a program that does it that's part of the bootstrapper package in Visual Studio. (I was ragging him about how difficult it is to install SQLServer.)
Writing code in a .NET application to connect to and use a SQLServer database is not version-specific, and Microsoft is committed to maintaining backward compatibility.
Package Load Failure
Package 'Microsoft.VisualStudio.Xaml' has failed tot load properly. . . yadda, yadda, yadda.
So now what? This package is somewhat important since I was hoping to do some WPF stuff this afternoon. Tried running without it and my XAML design view is gone.
I already tried "devenv /resetsettings" from the command prompt.
Thanks,
Scott
Try repairing the install.
Control Panel
Add Remove Programs
Select Visual Studio 2008 and choose "repair"
Did you recently install any updates to Visual Studio or any Add-Ins? If so can you please list them?
Install SP1: http://www.microsoft.com/downloads/details.aspx?FamilyId=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en
I had this problem after a fresh install of VS2008 Team System. Tried loading the updates, running setup, re-installing. No luck.
Installed SP1 and bingo! No more package load failures.
I -FINALLY- saw this error going into Tools|Options|Environment Fonts and Colors after trying everything I could think of to get it not to crash when I chose Tools|Import and Export Settings.
I had this problem when I installed Visual Studio Professional.
My theory was that it was because I already had Visual C# 2008 Express Edition installed.
Once I uninstalled both then reinstalled Visual Studio Professional it worked.
This is consistent with the OP's solution, which was to uninstall anything else which implemented XAML functionality.
In my case, just reinstalling SP1 didnt worked
Then i saw ive had two languages mixed in the IDE. So ive checked the installed programs and found:
Microsoft Visual Studio Tools For Applications 2.0 ENU
Microsoft Visual Studio Tools For Applications 2.0 Language Pack - ESN
When ive uninstalled the additional pack, the design views started to work again
In my case the machine.config file had gotten some bad XML due to a recent installation. There were two closing tags. After we corrected the bad XML, .NET works just fine.
Thank you Abraham for the hint. I was missing an end tag in my .NET 2.0 x86 machine.config.
However I had already spent hours repairing, uninstalling, installing and installing service packs.
WOULDN'T IT BE NICE IF VISUAL STUDIO 2008 GAVE A "MACHINE.CONFIG" CORRUPT ERROR!