I am using the InstallShield Limited Edition which comes with VS 2012 (after install). Anyway I would like to know how to specify the Content Source path on my target system to be on a different drive than the C drive. Specifically I want my content files to be at D:\MyAppFolder.
Related
I have a C# class library that references System.Data.SQLite (from nuget). This is the structure of my bin folder after build:
MyProject.dll
System.Data.SQLite.dll
x86/SQLite.Interop.dll
x64/SQLite.Interop.dll
System.Data.SQLite needs the SQLite.Interop to run and the correct dll is found at run time. However, when I generate a setup with InstallShield that includes the project primary output, the x86 and x64 folders are not copied and my application fails to run.
There is any way to force Visual Studio to include x86 and x64 folders in the primary output?
There is any way to include the folders manually in the InstallShield with relative path?
My environment:
Visual Studio 2012 Professional
Install Shield 2013 Limited Edition (Free)
System.Data.SQLite 1.0.96
Yes, there is a way to add/deploy folders through InstallShield. Under the Files tabs you can add the files/folder. While adding these files you can set relative path as well in this. Just set a property with the path and use that property in your relative path. So where do want to copy these files (reference locations for DLL), you can add that folder structure through InstallShield and you can add files in that.
I just ran across the same problem using VS2013 / Installshield LE; I ended up opting for changing the NuGet package on my machine to NOT create the x86 folder for the SQLite.interop.dll under the build folder.
To do that, look in the "packages\System.Data.SQLite.Core.1.0.104.0\build" folder under your project directory. Then pick the subfolder pertinent to the version of .NET you're targeting, and open the "System.Data.SQLite.Core.targets" file in a text editor. You'll want to delete all references to "%(RecursiveDir)" EXCEPT in the "SQLite Interop Library Content Items" section. Save, clean, and rebuild - the interop dll should now be in the same folder as the main executable/etc, and Installshield should be able to automatically include it as a dependency.
If it doesn't show up in the right place, try editing a different .NET version's .target file until you hit the right one.
I have SharePoint Foundation 2013 installed in the windows server 2012.
Is it possible to develop SharePoint solution/web parts/Apps using Visual Studio 2012 in my local machine(Windows 7 64Bit) without having SharePoint installed in local machine?
if i need to develop SharePoint solution/web parts/Apps in visual studio 2012, do i need to install visual studio in the Server that contain share point Foundation 2013?
Cant i develop in local machine and deploy it to server?
Can someone help me on this issue?
Thanks.
Try this;
• How to Perform SharePoint Development On A Client Workstation
15 Feb 2011 by Bryant Sombke in Guides, Web, Windows 16 Comments
One of the most difficult restrictions for a SharePoint developer to deal with can be the requirement to do development on a SharePoint server. Personally, I prefer doing my development on my local machine, eliminating the need to establish a remote desktop connection to a different machine in order to write code.
Unfortunately, SharePoint development requires many DLL files which are included with an installation of SharePoint on a server. To make matters worse, SharePoint 2010 requires an x64 server, further complicating the issue. Fortunately, there is an easy workaround that can allow a SharePoint developer to be productive, even while using their laptop on the road without an available internet connection.
Copy the SharePoint DLLs
As I mentioned before, SharePoint development requires DLL files that are included with a SharePoint 2007 or 2010 installation. The first step is to grab these off of a SharePoint server. For SharePoint 2007, they are located in the hive at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\, and for 2010 at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAP\. Copy the DLL files in this directory from the server, and paste them at the exact same file path on your local machine. Since your PC likely does not have SharePoint installed, you may have to create the directory structure yourself.
SharePoint 2007 DLL Directory
Register the Assemblies to the GAC
Now that you have the DLL files on your workstation, you will be able to include them as references in your Visual Studio projects just as you would with any other DLLs. However, if you want them to auto-register with your project when you use a Visual Studio 2010 SharePoint template or a WSPBuilder template, you must register the DLL files in your local Global Assembly Cache. To do this, open the directory on your workstation that contains the SharePoint DLLs and drag them into the C:\Windows\assembly\ directory. This will register them with the GAC on your workstation, and Visual Studio should successfully find the assemblies when a template is loaded up. Although these assemblies may be 64-bit, this will work fine even though your workstation may be 32-bit.
Global Assembly Cache
If you’ve successfully completed the two steps above, you should be able to write your code and successfully compile your project. Once you generate your WSP file, you can then deploy it like any other WSP.
Please Use Caution
If you do development for both 2007 and 2010, you can do this for both on the same workstation; just be sure to complete both steps for each version. Since the 2007 and 2010 assemblies have different Assembly Versions (12.0.0.0 and 14.0.0.0), you don’t have to worry about conflicts in the GAC. Be sure to use caution, however, because in my experience, Visual Studio tends to grab the SharePoint 2010 version of the DLL even for a SharePoint 2007 project if they’re both registered on your workstation. If this happens, remove the incorrect reference, and add a reference to the correct 2007 DLL from your 12\ISAPI directory.
From http://www.techerator.com/2011/02/how-to-perform-sharepoint-development-on-a-client-workstation/
You can develop SharePoint Apps from anywhere -- this is even more convenient when you're using the SharePoint 2013 development site template to do your testing on.
For farm/sandbox solutions things get more complicated...
If you want to develop webparts or other farm/sandbox solutions you need to have visual studio and sharepoint installed on the same machine (visual studio depends on the sharepoint dlls to build and debug properly). You also need to run Visual Studio as an admin for this scenario (so you'll need to be a local administrator for the machine in question).
It's possible to run SharePoint 2010 on Windows7, but this is not supported by SharePoint 2013 -- you'll have to run Windows Server for the development machine.
You can move your files from a development environment to your production SharePoint farm by building a WSP file for your farm solution on the development machine then sending it to your farm admin who can then deploy it to the production sharepoint environment... For a sandbox solution the site collection admin can add the solution file (WSP) to the site collection 'solution gallery' then active it (for more info on sandbox solution installation see the msdn documentation here: http://msdn.microsoft.com/en-us/library/office/gg615450(v=office.14).aspx)
Hope that summary helps, for more info on setting up development environments see: http://msdn.microsoft.com/en-us/library/office/ee554869(v=office.15).aspx
Yes, you can definately develop SharePoint solutions from your local machine where you dont have SharePoint installed.
For doing this you need to follow some steps -
Go to the server where SharePoint 2013 is installed and follow steps from 1 to 3
Go to Run and type "regedit"
Navigate towards HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office
Right click on 15.0 and click Export. Save the exported file
Now go to your machine where sharepoint is not installed and follow below steps:
Now open Registry on your machine
Import the 15 directory which was exported from SharePoint server
Open Powershell
Run this command
Set-ItemProperty -Path "HKLM:\Software\Microsoft\Shared Tools\web server extensions\15.0\" -Name "Location" -Value "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\"
Now open visual studio 2013 and you will be able to create SharePoint 2013 project without error.
PLEASE HELP!!!!
MY SET UP
Visual Studio Ultimate 2012 Update 4 on Windows 7 Professional,
ACTION
Installed latest SQL Server Data Tools Update
SYMPTOM 1 (Cannot create)
When attempting to create new project, I get:
Could not load file or assembly
'Microsoft.Data.Tools.Schema.Utilities.Sql.11, Version=11.1.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its
dependencies. The System cannot find the file specified.
SYMPTOM 2 (Cannot open existing project)
When attempting to open an existing project, I get:
Unsupported
This version of Visual Studio does not have the following project
types installed or does not support them. You can still open these
projects in the version of Visual Studio in which they were originally
created.
Non-functional changes required
Visual Studio will automatically make non-functional changes to the
following projects in order to enable them to open in this version and
Visual Studio 2010 SP1. Project behavior will not be impacted.
WHAT I HAVE TRIED
I have uninstalled/reinstalled VS2012, SSDT, and Update 4.
I've gone through "Programs and Features" Control Panel and have Repaired everything in several different orders.
I have been all over the internet and have tried every single workaround from every article even remotely related to my situation, including deleting temporary files, registry keys, etc.
Nothing seems to work.
Please help me, I'm on day 2 of being dead in the water.
MICROSOFT -- HEADS UP!!!
This appears to have worked !!!!
Zip up the folder C:\Program Files (x86)\Microsoft SQL
Server\110\DAC\bin and set aside (in case this doesn't work for you)
Delete the contents of C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin
Copy the entire contents of
C:\Program Files(x86)\Microsoft Visual Studio\11.0\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\120
into C:\Program Files (x86)\Microsoft SQL Server\110\DAC\bin
Re-launch VS2012,
AND
I was able to create a new SQL Server Database Project, and
I was able to open one of my existing projects.
VS did crash once when i was looking through my project using the SQL Server Object Explorer, but I have not been able to duplicate it.
How do we find the Visual Studio Installed using Inno Script.e VS 2005/2008/2010/2012.?
And how to run a particular batch file for different Vs.?
Let us suppose i want to run Install_Help_Vs2010.bat if Vs installed is 2010, Install_Help_Vs2012.bat if Vs installed is 2010 and so on.??
You need to check the registry keys.
Read the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0 -> InstallDir key.
(There may be Wow64 redirection on 64bit Windows - take care!)
The result looks like
e:\Visual Studio 2010\Common7\IDE\
which is path to Visual Studio.
10.0 in registry key is a variable which is dependent of Visul Studio version:
for Visual Studio 2005 - 8.0
2008 - 9.0
2010 - 10.0
2012 - 11.0
2013 - 12.0
To launch the .bat file simply use Exec() function: http://www.jrsoftware.org/ishelp/index.php?topic=isxfunc_exec
I cannot post whole script example as correct usage depends on the way how you handle your .bat files.
Are .bats already included in your setup or they are created dynamically (e.g. path to VS is read from registry and written into .bat file)?
And where are they stored? In some temporary folder or in VS folder or in application folder?
But basically you need to do simple if() conditions or case() switch and create/execute appropriate .bat file.
I am running visual studio 2012 on my windows 8 laptop, and I want to move the visual studio 2012 that holds the templates, projects, settings, etc in My Documents on a folder on my c: drive called Dev. When I copied the folder over to the Dev folder and deleted the original, an error message showed up when I ran vs again, and it created another visual studio 2012 folder in My Documents.
Click Tools>Options then Projects and Solutions change your Projects location path. There is a separate setting for project templates and item templates on the same screen.