I am using TFS 2017 update 2 on premise for CD .Log window is not working when i open the log for the completed release. Please refer the below screenshot
https://i.stack.imgur.com/KAD79.jpg
"Advanced Code Editor " Extension is enabled.Let me know how to proceed on this
Take a look in the _admin/_extensions page, if there list the Advanced Code Editor Extension already.
Try to disable and then re-enable it, see if it do the trick.
If above step do not work, try to directly delete the extension, this left the Legacy Extensions area empty. Finally check the release log window again.
Update
Reinstall the Legacy Extension,all you have to do is this:
Create a manifest.xml file with the following contents:
<Extension name="Advanced Code Editor Extension" id="{70D19AD3-93FA-437B-8CCE-CD80AA405F69}" version="1.0" min-host-version="11">
<Description>Provides advanced source control file and diff viewers to TFS</Description>
<Vendor>Microsoft</Vendor>
<Integrations>
<Frame end-point="tfs.source-control.file-viewer" url="{TfsRootPath}_BuiltInExtensions/_CodeEditor/Edit">
<Properties>
<Property name="name" value="Advanced Code Editor"/>
</Properties>
</Frame>
<Frame end-point="tfs.source-control.diff-viewer" url="{TfsRootPath}_BuiltInExtensions/_CodeEditor/Diff">
<Properties>
<Property name="name" value="Advanced Code Editor"/>
</Properties>
</Frame>
</Integrations>
</Extension>
Then go to your [tfs-url]/tfs/_admin/_extensions page and at Legacy Extensions pick the manifest.xml file. The Advance Code Editor will get installed. (again). Enable it and check if the issues are gone.
Related
I am using Visual Studio 2019 and trying to exclude wwwroot\js\src files from getting copied to IIS when publishing. Similar questions have been asked but those what I have referred to don't work because some of the project file syntax shown in those examples are not valid. Even the Microsoft documented method is not working.
MS Official documentation - wpp.target files has no effect on publish. It still copies the wwwroot\js\src files.
This - In vs 2019; CopyToPublishDirectory is not a valid attribute to Content tag. However the valid syntax below:
<ItemGroup>
<Content Update="wwwroot\js\src\**">
<CopyToPublishDirectory>false</CopyToPublishDirectory>
</Content>
</ItemGroup>
still publishes the js\src folder to IIS.
This - doesn't help either.
This must be quite a simple task and yet not straight forward way to get it done. Any help is appreciated.
Well,
This syntax worked after I add it to the csproj file. However the according to intellisense says it's invalid, but it works. Seems to be an issue on Microsoft side
<ItemGroup>
<Content Update="wwwroot\js\src\**\*">
<CopyToPublishDirectory>Never</CopyToPublishDirectory>
</Content>
</ItemGroup>
The tooltip says CopyToPublishDirectory can only have a boolean value of true/false
and If I do that this doesn't work!
I just upgraded to the latest version of WebEssentials v3 and the TS files in my ASP MVC 4 project aren't compiling to JS anymore. I verified that the Options --> Text Editor --> TypeScript --> Project --> Automatically compile TypeScript files which are part of a project option is checked, but nothing happens when I save or compile my project. I've tried deleting the existing .js and .min.js files that WE2 created, but that didn't help. I tried adding a new TS file to my project that and didn't generate a JS file. I reinstalled TS 0.9.1.1 and that didn't help.
Sooooo what to do? Am I missing something obvious? Is something not working or do I just have the wrong expectations?
Do I need to go back to WE2?
Update: I even created a brand new ASP MVC 4 C# project to verify it wasn't just my original project, but I got the same results.
Interestingly enough, I just created a new TypeScript project and my TS files compiled properly on save... So that's interesting..
There are some links in the change log of WE3, here is the one describes how to enable the compile-on-save feature, see http://typescript.codeplex.com/wikipage?title=Compile-on-Save for details.
I've created a nuget package called Ltc.MSBuild.TS0911WE3.targets which will do the trick for you, just open Package Manager Console, type in Install-Package Ltc.MSBuild.TS0911WE3.targets!
Go to Ltc.MSBuild.TS0911WE3.targets on nuget.org.
I'm not sure if this is the correct method of dealing with the problem, but here's what I did to get "compile on save" working on my project...
After noticing that Compile On Save worked when starting from a new HTML Application with TypeScript project, I did a comparison between that and my non-working ASP MVC project. Turns out, my ASP MVC project was missing this bit of code..
<PropertyGroup Condition="'$(Configuration)' == 'Debug'">
<TypeScriptTarget>ES3</TypeScriptTarget>
<TypeScriptRemoveComments>false</TypeScriptRemoveComments>
<TypeScriptSourceMap>true</TypeScriptSourceMap>
<TypeScriptModuleKind>AMD</TypeScriptModuleKind>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)' == 'Release'">
<TypeScriptTarget>ES3</TypeScriptTarget>
<TypeScriptRemoveComments>true</TypeScriptRemoveComments>
<TypeScriptSourceMap>false</TypeScriptSourceMap>
<TypeScriptModuleKind>AMD</TypeScriptModuleKind>
</PropertyGroup>
<Import Project="$(VSToolsPath)\TypeScript\Microsoft.TypeScript.targets" />
Copy/pasting that into my ASP MVC project gave me Compile On Save support again. Of course, it's still not exactly what I expected. The resultant JS files are not added to the project automatically, so that's something I had to do manually. I also had to manually group the JS file with the TS file to mimic the same experience I was getting with WE2.
Hope that helps someone. Would love to hear some feedback on the solution.
Make sure your .proj file has a TypeScriptCompile XML section. You can copy from the typescript project if its not present.
Here is the specification : https://msbuildtypescript.codeplex.com/
using the "web essentials" tool (free, recomended) enable the preview pane in the web essentials options
Tools --> Options --> Web essentials --> Typescript: Show Preview Pane[X]
Now every time you save an open TS file, web essentials makes sure the file compiles (so it can display it) and you can update your javascript code while the project is running.
Is there a way to disable code analysis (the light bulb) in IntelliJ? I really don't care about code improvement suggestions as I'm viewing some third party code. I've already unchecked everything single feature in Project Settings -> Inspections.
I'm using IntelliJ 10.5 to edit ActionScript code.
On the status bar, there is a little icon showing a man. If you click on it, you can change the inspection level: nothing, syntax, full analysis.
To disable inspections:
Settings > Project Settings > Inspections
Click the 'Reset to empty' icon (looks like an eraser)
To disable intentions:
Settings > IDE Settings > Intentions
Uncheck all of the boxes here
I have concluded that it's not possible to completely disable Inspections in IntelliJ 10.5 (at least while editing ActionScript) possibly due to a bug.
Follow-up: IntelliJ support is saying this may be a bug.
Edit April 2017: Finally there is a workaround, in particular add:
<option name="SHOW_INTENTION_BULB" value="false" />
to IdeaIC2017.1/options/editor.xml. If there's no editor.xml then create a new one as such:
<application>
<component name="EditorSettings">
<option name="SHOW_INTENTION_BULB" value="false" />
</component>
</application>
I believe you're looking for "Intentions", not "Inspections", though I don't know a way to turn them of globally.
Windows Installer 5 added support for the Hyperlink control which I would like to utilize if available. I cannot set a dependency towards Windows Installer 5 (doesn't support WinXP), but I would like my installer to be able to utilize the hyperlink control if Windows Installer 5 is available when running the installer.
How do you manage to do this? Conditional imports of fragment files based on the versionMsi property? A Google code search or regular Google search didn't reveal many samples.
You'll want to read this article:
Careful with that Hyperlink (on your MSI dialog)
The summary is you create two nearly idential dialogs and create mutually exclusive control events to drive which one gets displayed based on your MSI version.
I am using WIX Installer and used this code. Wix is a free open source tool and is same like the costly other tools. I used this code for hyperlink and it works perfect
<Control Id="MyHyperlinkControl1" Height="20" Width="100" Type="Hyperlink" X="5" Y="105">
<Text><![CDATA[Stackoverflow]]></Text>
</Control>
My view has errors. I see these errors only if I open the view in Visual Studio.
I would like to see the errors on compile time rather than on execute time.
Does exist a way to obtain this behavior?
You can update by hand the .csproj file and add a <MvcBuildViews>true</MvcBuildViews> that will compile the views as you go.
Here's a link I googled, you'll find others as well.
EDIT: If it's too slow try setting the build only for Release, edit the csproj file doing something like this; see the docs for AspNetCompiler for more details.
<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.Common.targets.
-->
<Target Name="BeforeBuild">
</Target>
<Target Name="AfterBuild">
<AspNetCompiler VirtualPath="Temp" PhysicalPath="$(ProjectDir)\..\$(ProjectName)" />
</Target>
I assume you are talking about C# compile errors and not things like CSS validation errors.
One thing you can do is add a Web Deployment Project to your solution. When it builds, it will run aspnet_compiler.exe on your project which will expose any of these C# compile errors in .aspx files that otherwise wouldn't be indicated until the .aspx file was compiled on the fly at runtime.