I would like to create my setup to install my application developed in VS 2012. The application needs to be installed in Program Files folder, so it needs to always run with administrator rights. I have created a new InstallShield project inside my solution, but I don't know if it is possible to set some settings to allow that exe always runs as administrator.
I'm using the InstallShield 2013 Limited Edition
You can only manifest an EXE to indicate to Windows that the EXE requires administrative privs. You can't simply bypass windows security.
Related
This is a bit of an odd one.
I am running Visual Studio 2019 Enterprise in a VM in Azure, and whenever I elevate to Admin any files that I build/save are locked by my user, i.e. I right-click on File Properties -> Security -> Advanced my user is the owner, but there is a shield icon next to it. This is causing me problems as when I run Visual Studio un-elevated I can't save the file until I have removed the shield icon by re-taking ownership. On other machines running Visual Studio 2019, I can do this without having to reset the permissions. Both machines have Windows 10 Pro with 1909 Build 18363.836 and both are set to be in Developer mode. The project accessed from the root of the C: drive.
i got a simple question
I have a server, i access it via remote desktop, when i try to create a new WebPart in visual studio 2012 got this error :
i tell my IT administrator, to give me the rights privileges,
He said he can't give me the administrator rights and, he tell me to find another way to create my sharepoint's developments.
And he don't want to create an AD group and create rights privileges.
So my question is : There is another way to create WebParts or other developments without the administrator rights ?
To develop SharePoint solutions in Visual Studio on Windows Vista and Windows 7 systems, UAC requires that you run Visual Studio as a system administrator.
http://msdn.microsoft.com/en-us/library/vstudio/ee231582(v=vs.110).aspx
Are you running your VS application as administrator?
Right click on your VS application to find the below options.
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.
I have a windows form project and I want to create an installation package for this project. How can I create a setup file in Visual Studio 2012 ? My project is without data base.
How to create a Setup package using Visual Studio 2012.NET?
Microsoft released the Visual Studio Installer Project extension in April of this year, the catch is it's for VS2013, not VS2012.
http://blogs.msdn.com/b/visualstudio/archive/2014/04/17/visual-studio-installer-projects-extension.aspx
The 'lite' InstallShield option remains in VS if you need something with more flexibility.
Advanced Installer also has a free version that includes an extension for VS. This is a commercial tool but the extension is included in the free edition as I said, for more advanced features you need to purchase a Professional or higher licenses and edit the project direct from Advanced Installer GUI, not from VS. (but you can still use the project in the VS solution, so you get the MSI built at the end of your build process)
Visual Studio setup projects (vdproj) are not supplied with VS 2012
There are several solutions for you:
You could use InstallShield instead.
If you don't want or
can't use InstallShield for any reason, you could try WiX. This
toolset builds Windows installation packages from XML source code.
If you only use Windows Presentation Foundation (.xbap), Windows Forms (.exe), console application (.exe), or Office solution (.dll) you could look at ClickOnce. To use this you should right click on the project file in the solution explorer and select "Publish" from the pop-up menu.
Alternatively you can use previous version of Visual Studio (2010).
I wanted to deploy my application which uses crystal reports and SQL Server express.
How can create an installer which can create the databases and configure the app.config files on installation?
ClickOnce will not allow you to easily run db scripts upon installation. You will have to use a VS Setup project or a tool like InstallShield that provides much more control over the install process..