I would like to know if there is a way to set a certain Project Collection to be the default Project Collection in DevOps when a user uses the main DevOps URL?
Related
I'm using the experiments page of a project in ClearML Web UI to visualize some custom metrics. Therefore I've customized my table vie (https://allegro.ai/clearml/docs/docs/webapp/webapp_exp_table.html?highlight=customize#adding-metrics)
But whenever I leave the page for another project and go back, the table will be resetted.
Is there a way to store configuration for a specific project?
Disclaimer I'm part of the ClearML (formerly Trains) team.
The layout for the table is stored by the Web UI on your user-preferences on the clearml-server, but it is not unfortunately a per project setting. This means that if you change the lable-layout in one project it, it will become the default table layout. I suggest you put feature request on the GitHub repo, it sounds reasonable to add.
I am trying to publish a project to azure. I want to re-use a web app. But I don't see the parent Resource group eve. Any ideas? Here is a picture:
missing rg
That can be for different reason. but that happen to me was that the Azure web app resources that I created in AZURE was configured with a different NET framework that the application that I was trying to publish. In this case don't see the Web App and also not resource group.
Go to Azure portal and take a look to your WEB APP framework configuration at:
Change it to your use net framework if it is different.
Is there a way to host the new work item web form for Visual Studio Team Services and TFS 2017 (Link) within a custom page that my application has? Basically I'd like the users to use my custom web page to create new work items in TFS or Visual Studio Team Services as I do certain pre and post processing on work item that is created using my application. For this I would need to
Somehow host the web form on my own page
Hook into pre and post save events (if any) of the web form to do the pre and post processing.
I don't think you can embed the new work item form directly within a custom page as the work item form is based on the TFS process and wit definitions.
I can think of is that you can try to write your own extension and call the REST API to create the work item in the custom web page. See Create your first extension - Call a REST API
I am working on an asp.net solution and using my remote testing environment with godaddy.
The application is ready for deployment so i have two questions:
1- since the database will be different , i am thinking about using a different Web.config , but not sure how does it work and how to implement that so i can choose easily which web config depending on the poriject/solution
2- the solution i am working on could be personalized and deployed to multiple clients , so each client version will be different (Like the logo and other stuff not the design and functionality), do i need to create separate solution for each client or should i create a separate website project instead?
what's best practices in this case
Use configurations and associated config transforms. By default, your project gets a Debug and Release configuration, but you can add additional configurations. Then, for each configuration, you can have a separate Web.config transform, Web.Server1.config, Web.Server2.config, Web.Client1.config, Web.Client2.config, etc. When publishing, you choose which configuration you want to publish with, and that associated transform will be run against the Web.config file to change out connection strings, app settings, whatever.
For more information see: How to: Transform Web.config When Deploying a Web Application Project | MSDN
I find this odd given that a Web API project should really be a view-less MVC 4 Web API based project. Is there any reason for these projects to contain these files by default? I would like to eliminate them all (*.js, *.css, etc.), any reason not to?
These files are included to build the "normal browser" view, this is the page wich you see if you navigate to your host without the "/api" call in your url
You could remove these files if you don't want to use their functionality.