websharper for VS Express 2012 - visual-studio-express

Is it possible to use WebSharper with VS Express 2012?
I read Websharper templates for F# Tools for Visual Studio 2012 Express for Web and wanted to try. So I installed WebSharper, then found folder with WebSharper templates, but don't know where I should copy them.
Anybody tried?

I found where you should put WebSharper templates. It should be in folder for project templates, specified in Tools -> Options -> Projects and Solutions -> General -> User project templates location:
After I copied templates there, they are available when I create new project.

Related

Problem building a Wix wxs file in Visual Studio 2017

I just installed WiX on my machine and then installed the extension for Visual Studio 2017. When I attempt to build the Product.wxs I get "Could not find wix.targets at ''" back. I can run a build from the command line using candle and light, but I need to be able to do this with VS. Is there a place I can configure Visual Studio to look for the wix.targets file. I'm guessing that is the problem since it looking at '' for the file.
Create a WiX v3 project not v4.

How do I configure the Razor *.cshtml editor's C# compiler settings outside of an ASP.NET project?

(This is not a duplicate of Print and/or modify the c# version that the razor compiler service uses to compile cshtml because I'm using RazorGenerator, not ASP.NET, the translation from .cshtml to .cs happens every time I press the Save button in Visual Studio, so adding assembly references or NuGet packages to my project won't help)
I have a C# Class Library project using RazorGenerator (a Visual Studio extension that transpiles .cshtml to .cs sources). RazorGenerator itself works fine and my .cshtml files are converted to cs correctly without any problems considering I'm using C# 7.3 language features and types defined in custom assemblies.
The problem is Visual Studio's own .cshtml designer (independent of RazorGenerator) seems to default to the C# 4.0 compiler version and doesn't even load System.Core.dll - so when viewing .cshtml files in the Visual Studio editor I get peppered with error messages that shouldn't be there:
"Feature 'out variable declaration' is not available in C# 4. Please use language version 7.0 or greater."
and broken namespace imports because it isn't loading assemblies:
I saw these SO posts:
Where to configure Razor page language version to C# 6?
C# 6.0 Features Not Working with Visual Studio 2015
...which suggest adding the NuGet Microsoft.CodeDom.Providers.DotNetCompilerPlatform package to the project and restarting Visual Studio, however that did not solve the issue.

Use a SSIS package as Template in SSDT for Visual Studio 2017 Community

. Hi everybody!, I'm running into a small problem.
I have VS 2017 Community Edition, I've installed SSDT (SQL Server Data Tools)
I've built an SSIS package (a generic one) and now I would like to use it as a template for future packages.
So, I was digging in the web, also here in StackOverflow and found for example this article:
Setting up SSIS Item Template in SQL Server Data Tools for Visual Studio 2012
I found lot of other articles in MS for example:
https://learn.microsoft.com/en-us/sql/integration-services/create-packages-in-sql-server-data-tools
others, etc. and followed up to the tee but, for some reason I can't make it work.
This is my folder structure for my VS installation
I've left out of the tree some folders that doesn't apply to the problem
I put my package in the places I found in the articles and didnt work.
Sometimes, in the articles mentioned folders that I didn't have so I created and tried but nothing also (so deleted this folders)
I'm really lost, I tried everything I read, and some "creative things" from my yard but no results.
Anyone has come through this or has some experience about this issue?
Anyone can help?
Thank you very much.
Best regards and Happy new year!!
Gabriel
Well based on the articles I've read and the help of #billinkc, I finally figured out where to put the package, I was missing something also, but I realised when I read #billinkc answer.
When you are on VS Community Version, you have to put the package in this path:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\SSIS\ProjectItems\DataTransformationProject\DataTransformationItems
The files you need to make it work are, a dtsx file (the package that will be the template) and a vsdir file which mainly needs to have this structure I used this values and worked fine:
YourPackageName.dtsx| |The name you want to appear|100|The description of the package| |21| |#44
You can check all the fields of the vsdir file in the MS documentation:
https://learn.microsoft.com/en-us/visualstudio/extensibility/internals/template-directory-description-dot-vsdir-files
So now I have it running!
Thanks for your help!!
I don't have 2017 installed but this appears to work for 2015 so if you don't mind being a guinea pig...
Close out all instances of Visual Studio
Copy your template package into Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems
Open your SSIS project
Right click on the project and select Add, New Item and you should have your template package listed (TemplatePackage2)
For reference, below is what my folder structure looks like. Since I couldn't remember whether the package templates lived at DataTransformationProject or DataTransformationProject\DataTransformationItems, I put a copy of my template package in both, varying by name to see what was picked up in the editor
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationProjectItems.vsdir
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\TemplatePackage.dtsx
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems\DtsProjectItems.vsdir
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems\TemplatePackage2.dtsx
General notes about templates
The first is that the only way to get to your template is through the click path described above. If I want to add a new package, my default click path is right click on SSIS Package and select "New SSIS Package"
Pre-2012, the internal IDs of components and the package would remain the same. BIDS Helper had functionality to address this. Why it mattered was if you were attempting to track performance for packages, if they all report the same GUID you're going to have a hell of a time discerning whether Data Flow Task that ran for 10 hours is the same one that normally takes 10 seconds or was a second (different) package executed.
Developers will need to be local administrators on their machine to deploy the template package(s) and you'll need a process to keep that up to date. That or you need to engage the network admins to get these copied to developer machines.
Finally, if I had template logic, I'd probably abstract that away into Biml and then use source control to ensure people are working with the current version and avoids the whole permission issue.

Building SSIS .dtproj inside a VSTS Hosted Build Agent

I'm trying to build a SSIS 2016 project, that's been configured with the Project Deployment model in a VSTS build with the intent to deploy the .ispac file onto a SQL Server VM hosted in Azure.
Using MSBuild to build the project file returns the following error:
The default XML namespace of the project must be the MSBuild XML namespace.
If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element.
If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
I found a blog post here describing the same issue
https://speaksql.wordpress.com/2013/06/07/a-journey-to-db-deployment-automaton-ssis-build-using-msbuild/
However, the solution depends on installed SQL Server Data Tools into a build agent.
Is there a method where I can use a VSTS Hosted agent, and not have to create an on-premises agent with SSDT installed?
Just released new Extension for VSTS/TFS
https://github.com/ToxicGlobe/VSTS-SSIS-Extension
It build Visual Studio project, containing packages and parameters to a project deployment file (.ispac)
https://marketplace.visualstudio.com/items?itemName=TG.VSTS-SSIS
For similar scenario i used devenv.exe
Tool : C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Arguments : .\Code\Database\NameOfSolution.sln /build $(BuildConfiguration)
devenv.exe /build does not require ssdt to installed on build agent
Looks like Microsoft is not supporting this just yet based off UserVoice
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/11543292-install-sql-server-data-tools-ssdt-for-sql-serve
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/4850300-install-sql-server-data-tools-for-bi-on-the-team-f

How do you define a default html in silverlight?

How do you define a default html in silverlight?
In the Microsoft Development Environment, Microsoft Visual Studio, when I build a silverlight project, the code auto-generates an HTML file in the Release directory (and in the Debug directory)
Yet, I have seen some projects that have a Default.html file among the project files. And when I run the program in debug mode, the default.html comes up.
How is this done? Where is the settings which tell Visual Studio which html to use when running or debugging. In another project, when I create a project from scratch, the program runs a generated html in the debug or release directory.
How do I include my own html in a silverlight project?
In the project settings, I found you can unselect the option to have the compiler auto-generate an html or use one that you define.