I have been exploring the PowerBI visualizations github project and starting to make my own visualization but I'm having the following issues that is really slowing me down on the development:
It takes almost 3m to run the "build", is there any other option for rapid development because when we are starting with the project 3m see the results of the code changed is too much...
Is there any way to debug the visualizations inside the framework? I had setted the property "DEBUG" to false in the gulpfile.js but without success...
Thanks!
If you are a windows user then just use Visual Studio 2015 solution PowerBIVisuals.sln from src/ folder
It has continuous build support, so that when you open the solution it will run continuous_build_debug task.
If you are a Unix/Linux/Mac user then you'll need to manually run continuous_build_debug. (Run "gulp continuous_build_debug")
This task will run Watchers which will build project parts after you save changes to any file.
Related
I am just trying to understand the whole build/publish topic for .NET Core and was playing around with one basic console application.
When I build the app
dotnet build
and afterwards build it with release configuration
dotnet build --configuration Release
I receive errors saying
Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute
[test]
obviously the files
./obj/Debug/netcoreapp2.1/test.Assembly.info
and
./obj/Release/netcoreapp2.1/test.Assembly.info
store values for the same attributes:
What am I doing wrong?
Some further questions to get a clearer picture of this:
As a DEV, would I delete all Debug stuff before building for release?
What is the behind-the-scences difference between building for debug or release?
Why should I ever publish for (default) debug configuration (dotnet publish)?
I've read all the documentation from ms but imo its from and for people more familiar with building processes.
Thank you very much in advance
In short, setting GenerateAssemblyInfo to false in the relevant .csproj should do the trick:
<PropertyGroup>
<GenerateAssemblyInfo>false</GenerateAssemblyInfo>
</PropertyGroup>
See this git-issue
And this one
Short explanation:
.NET CORE first introduced the project.json based project system, which replaced AssemblyInfo.cs. Later, project.json was dropped in favor of a more extensive .csproj usage. Read more here
I'm trying this, I set up alwaysRun to true in cordova-uglify and ionic-minify folders, but the only way to see the files minimized and uglified is running ionic build android --release (but i don't want to generate the app for PRD yet)
If I do
ionic build android --minimize
The result is the full file, not minimized.
Any idea how to get the files minimized? I'm trying to fix a performance issue with this as the app takes 12 seconds to open and in all sites suggest this as a performance improvement.
We've got several thousand unit tests that run in one of our projects. These currently take over ten minutes to run, and I'm trying to reduce this time.
One of the things I'm looking at is determining which tests are impacted by the latest code changes and only run those impacted tests. This seems to be a feature that TFS has, but all of the tutorials are from TFS2010 and the old XAML builds and not for the new vNext builds in TFS2015.
Does anyone have any experience in getting this to work?
Following this tutorial:
https://msdn.microsoft.com/en-us/library/ff576128(v=vs.100).aspx
I've defined a .testsettings file, and referenced it from a .runsettings file, and then in TFS2015 build I've set the .runsettings file as the Run Settings here:
But there doesn't seem to be any test impact files generated.
Answer from Microsoft:
Hi Steve,
Thanks for your post.
I tested it in my TFS 2015 vNext build and received the same result.
It seems there’s no the Analysis test impact = True/False option in
TFS 2015 vNext build Test task, this option is exist in XAML build
definition.
For this scenario, please submit it to User Voice site at:
http://visualstudio.uservoice.com/forums/121579-visual-studio,
Microsoft engineers will evaluate it seriously.
https://social.msdn.microsoft.com/Forums/en-US/610e304d-608e-49e9-8fcc-e65617828a6f/determine-impacted-tests-during-vnext-build?forum=tfsbuild
As part of my war on long build times (our C++ solution takes about an hour to build using Incredibuild!) I'm trying to find the build time hotspots.
I've enabled Build Times logging (Tools -> Options -> Projects and Solutions -> VC++ Project Settings -> Build Timing) on my machine and that does what I want (I've then written a script to pull those out for each project and dump them somewhere more useful).
The trouble is I can't make out CI builds do the same thing.
We're using CruiseControl.Net (although I'm in the process of trying to persuade the team to move to TeamCity). The overnight build does not use Incredibuild, so this is ideal for my logging purposes.
CC.Net runs as a service using a dedicated system account.
I've logged into the server and launched Visual Studio using the system account and applied the "Build Timing" setting.
But the builds don't show the Build Time.
so:
(a) Is there anything special about running VS from a service that may have an impact?
(b) Is there anything special about running it from CC.Net (we're using the DevEnv task to build the whole solution - default install location - matches the one I set the option in)?
(c) Is there any other way I can coerce it into logging the build times (other than using MSBuild, which would be a big job right now)?
This might not give the amount of detail you need, but you could add the statistics plugin to the dashboard. It contains a graph of project build duration.
I'm trying to work out how to run xUnit tests from TFS 2010.
I found some articles on how to achieve that with the older version (http://jonnekats.wordpress.com/2009/05/07/integrate-xunit-tests-into-your-daily-team-build/, http://weblogs.asp.net/mehfuzh/archive/2009/08/25/configuring-team-build-using-xunit.aspx).
These approaches don't work anymore with TFS 2010 because builds are no longer MSBuild files but instead are Workflows with different tasks.
What I would like to achieve is something similar to what I've got on my dev machine:
- build everything
- run the .xunit project file
- check the results
All that I can see on the web are custom build steps which I can't/won't use because I'll have to configure them for each single unit test assembly and they'll probably get completely messed up in TFS.
Any input would be appreciated.
Why dont use "InvokeProcess" in TFS Build workflow and invoke xUnit command line interface with the necessary xUnit project files as parameters?
You can capture the output of the command line by setting InvokeProcess->stdout to write a build message.
Take a look at the xUnit work item Support VSTS Test Runner on codeplex. You can find there a VS2010 extension in Beta version.