I am planning to create new extension and want to support old Visual Studio versions (2005+).
Earlier I was able to generate PLK using https://vsipprogram.com/external/key that was hidden one day but still was available via this direct link.
Today this link is being redirected to new place and finally I get error 404, so not found.
Is there any way to get PLK today?
I wrote vsipinfo#microsoft.com as the page suggested, but they never replied me in the past. I can't believe I am the only developer who still wants to support old VS versions.
It's not a duplicate of Obtain a PLK for a 2005/2008 VSPackage because that answer doesn't work anymore.
How to generate PLK for Visual Studio extension nowdays?
You can try following method:
Enroll the VSIP Program (https://vsipprogram.com). The Basic Level is free. It takes a couple of days to get approval from Microsoft.
Click the "Support" link at the bottom of the main page to go to the FAQ section.
There is a "How do I get a PLK/SLK for Visual Studio?" FAQ entry that points you to the PLK/SLK generator tool.
Certificate: Obtain a PLK for a 2005/2008 VSPackage.
Related
All the msdn documents say I should have the following template options (see image below) when trying to create a new asp.net application but for some reason the only options I have are Empty, Web Forms, and Azure Mobile Service.
Does anyone know how I might go about restoring the missing options here as I need to create a new MVC application?
EDIT: Further clarification:
When following the steps carried out here ...
http://www.asp.net/visual-studio/overview/2013/creating-web-projects-in-visual-studio
... when I get to the above dialog I do not have any mention at all of both web API and MVC.
Finally cracked it ...
For some reason the web developer tools were not installed as part of my installation (likely due to the repair that happened last week).
So if anyone else gets this the fix is as follows:
Go to control panel > programs and features
Find "Visual Studio Ultimate 2013" entry.
Right click > change.
Click on "modify"
Tick the box labelled "Microsoft Web Developer Tools" and click to continue.
After running through the setup process everything should now be in place !
Wierd ... these options were in their correct place but apparently not after the repair !
Please ..Select WebForms-> Press Below Check for MVC (This optional u can leave it for now )-> Then you wil have an option for
MVC Application
WEB API application
ASP.NET WEB Application and so on!!
If no
reinstall or run some update for VS2013 ... its corrupted installation i guess or
clear APP-DATA ,TEMP AND MYDOCUEMNTS for VS related stuff...if u have massed it while working other settings...
Cheers!
UPDATE: see Microsoft's official response below. I imagine there is a non-offical hack to accomplish this, so I'm leaving the question up.
UPDATE 2: Vote up my WebDeploy feature request to Microsoft on this issue.
I use MSDeploy heavily at my shop, and have spent hours trying to define an msdeploy parameter that will modify an "additional provider setting" for a deployment provider at deploy time. I came up empty on this when searching online and with Reflector on the Web Deploy binaries.
Specifically, I'm trying to allow command line options to manipulate the "DropObjectsNotInSource" and "BlockWhenDriftDetected" settings for DacDeployOptions of the dbDacFx provider.
I've tried every XPath expression I can think of to modify the DACFx options like these from a manifest.xml file:
<sitemanifest>
<dbDacFx path="C:\Database.dacpac"
DropObjectsNotInSource="False"
BlockOnPossibleDataLoss="True" />
</sitemanifest>
Using the msdeploy setParam with the kind DeploymentObjectAttribute always fails to find any matching nodes on //#DropObjectsNotInSource.
I suspect it fails because the value of DropObjectsNotInSource is actually stored in the attribute "MSDeploy.MSDeployProviderOptions" for the provider's node within the package's archive.xml file. (This attribute value seems to be a .Net serialized instance of the Microsoft.Web.Deployment.DeploymentProviderOptions, so it would be quite difficult to manipulate it with plain old XPath.)
Is it possible to modify these additional provider settings at deploy time?
UPDATE: I sent an email to the Microsoft Web Deploy team via their blog as well as posting here. The Web Deploy team was awesome in getting a response to me (thanks Harsh and Ranjith!). Unfortunately, the official word is this is not supported.
From: Ranjith Mukkai Ramachandra ...#microsoft.com
Subject: RE: Can MSDeploy setParam modify "additional provider settings"?
Date: February 15, 2013 5:20:46 PM EST
To: Web Deployment Support
Hi Steve,
Sorry, this is currently not supported.
Thanks,
Ranjith
I have a classic ASP application written many years ago that I'm trying to fix.
The following lines recently stopped working after w7 sp1 was applied.
set address = Server.CreateObject("ADOR.Recordset")
count = lo_connection.GetRecordset(sql,address,false, error)
Set RDF2 = Server.CreateObject("RDSServer.DataFactory")
Set teststring = RDF2.ConvertToString(address)
It fails on the last line there saying "Microsoft VBScript runtime error: Class doesn't support Automation"
A bit of searching found several articles like this one
http://blogs.technet.com/b/asiasupp/archive/2011/03/14/changes-in-mdac-adodb-com-components-in-windows-7-service-pack-1.aspx
that described the problem exactly. Where I am failing is that none of the suggested fixes seems to fix the problem. Any suggestions?
The solutions described in the link are not relevant here, since ASP is not early-bound - it uses OLE Automation. It might be worth re-registering the component which creates RDSServer.DataFactory objects (which is C:\Program Files\Common Files\system\msadc\msadcf.dll on my machines).
I looked up this object, and I found this Microsoft web page:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms681447(v=vs.85).aspx
"This feature will be removed in a future version of Windows. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. Applications that use RDS should migrate to WCF Data Service."
Doesn't sound too good.
I am trying to deploy my first custom aspx page in sharepoint:
Windows Server 2003
Microsoft Visual Studio 2008
VSeWSS 1.3
Latest Sharepoint Patches as of May 28, 2009
I am following this detailed howto:
http://geeksconnected.com/jamil/Lists/Posts/Post.aspx?ID=19
Unfortunately, it quickly becomes incomplete toward the bottom. I am running into two issues thus far:
How do you grant the VSeWSS Administrator privileges so that the "Deploy" option will work in Visual Studio?
It cuts off half of the <SafeControl> tag in the example, and I am not sure what to put after the PublicKeyToken= option. All current attempts completely break sharepoint.
Any solutions and explanations would be appreciated. Thanks in advance for any help.
Do yourself a favor and use WSPBuilder and its companion SPVisualDev instead of VSeWSS. Both of these tools are on CodePlex.com
They will take care of your safecontrols problem by adding that into the WSP file that any SharePoint administrator can install. (Frankly, modifying web.config by hand in a SharePoint environment is a big no-no in my mind, especially safecontrols)
They will also not need the elaborate 2-project spoof just to have a codebehind for an ASPX page that the article you quoted promotes. SPVisualDev will give you the option to do 'add new item' in visual studio and select a new Page or UserControl with codebehind, and take care of the deployment through WSP. Easy as!
Did you follow the instructions for post-install configuration of VSeWSS 1.3? http://blogs.msdn.com/steve_fox/archive/2009/03/18/vsewss-1-3-post-install-configuration.aspx
You probably need an account which is allowed to run stsadm.
2.The safe control tag should look like the following:
<SafeControl Assembly="[Assembly Name]" Namespace="[Namespace]" TypeName="*" Safe="True" />
To get the public key token you first have to sign the assembly (properties on the project->signing). Then you can build it and drop in the GAC (C:\Windows\assembly) and read the public key token directly in your explorer window.
We are using SourceForge Enterprise Edition 4.4 in one of our project.
My question is, in CollabNet SFEE (SourceForge Enterprise Edition 4.4), how will we get attachments associated with an Artifacts Using SFEE SOAP API?
We have made our own .net 2.0 client. We are not using .net SDK provided by Collabnet,
If you commit with a message you can add "[artf1000]" (where artf1000 is your artifact number) to the beginning or end of your commit message. Then it will associate to that artifact you can also do this with documents using doc1000, to get the id of the item you can use the URL it is what is after the http://sfeeserver/sf/go/.
Documents and artifacts are the only item I have used this for so I am not sure about other types of links, but I would imagine anything that has a /go/ID could be referenced by the ID.
ie:
http://sfeeserver/sf/go/artf1000
http://sfeeserver/sf/go/doc1000
Edited to add:
I have seemingly successfully tried this with releases, tasks, and discussions as well.
You can cheat a little bit and have a look at the scripts from SFEE. Log into your SFEE via SSH and take a look at the following script:
/usr/local/sourceforge/sourceforge_home/integration/post-commit.py
Maybe it helps...