ON TFS2012 is it possible to request feedback from customers that are utilizing the web client without them having to install feedbackclient.exe on their machines
Usersnap allows customers to add feedback without installing anything locally. It integrates into Microsoft Team Foundation Service (this means, every feedback from your customers is automatically created as ticket inside your TFS workflow).
Your customers even don't need an account in TFS to provide feedback.
It's easy to integrate Usersnap with TFS, you can have a look at the docs here: https://usersnap.com/support/docs/apicfg#tfs
To work with the feedback request like it is explained here it is not possible to give feedback without installing the client tool.
I thought it would work also by logging in in the TFS web interface then open the feedback request and answer to it but apparently after testing it myself I did not found a solution directly. Though the feedback would be filled in completely manually while all the needed tools are available with the client tool.
Related
TFS 2015.3, on premises.
The REST API of TFS has an undocumented portion that deals with app pools: _apis/distributedtask/pools on the server level and further down. I can drill down all the way to agent details: _apis/distributedtask/pools/111/agents/222. Now, in the Web UI there are two collections per agent: requests and capabilities. Does anyone know the REST API URLs for those? Adding either /requests or /capabilities yields a "Document not found" error.
If the TFS API is somehow self describing, I have yet to discover how. I miss WSDL...
I opened up Chrome Network inspector and found that these are the API calls for Requests and Capabilities. These are from latest VSTS but I think the same will work for TFS 2015.3 also.
For Requests:
_apis/distributedtask/pools/1/jobrequests?agentId=1&completedRequestCount=25
For Capabilities:
_apis/distributedtask/pools/1/agents/1?includeCapabilities=true
Note: These are undocumented so you should be vigilant while upgrading your TFS if you are taking dependencies on these.
My question here is pretty simple: how to properly (and 100%) configure both Live Connect and project in Visual Studio 2013 in order for the local application run and authenticate an user properly against Microsoft account.
My question may be simple, but the answer is most likely not as simple. I've been reading countless articles and possible tutorials about this, but they are all fragmented and divided into small parts that do not really conciliate each other.
So below is the situation better described, with the steps I have followed.
[Steps Followed]
1) I have created a simple MVC application using Visual Studio 2013.
2) I have configured the project (using its properties) to use IIS Express with current Project Url : https://localhost:44302/
The project runs quite well, and external authentication with Facebook, Google and Twitter run very well too. Now for the tricky part:
3) I have created account with Microsoft and successfully created application in the Live Connect Developer Center.
4) Since configuring the field Redirect URLs to a simple http://localhost:<port> will not work (well...just because they didn't want it to, I suppose), I have additionally done the following..
5) Mapped in hosts file the following domain to localhost: # 127.0.0.1 mytestdomain.localtest.me
6) Reconfigured in Live Connect the Redirect URLs field to use the newly mapped domain: http://mytestdomain.localtest.me (although I have tried this with or without the port as well).
[End result]
With this configuration, the site runs properly locally. However, when I try to sign in with Microsoft account credentials (so, when I click the "Microsoft" button), I have redirected and received the following message:
"We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later."
I honestly do not understand why wouldn't this work, when a couple of articles suggested that doing these specific steps would make it work.
What can I be missing, why would this happen at all?
If someone can write here what am I missing and we could all join effort and create in this topic a full fledged, 100% working configuration for local application testing with Microsoft authentication, I believe it would help everyone. If such topic already exist and you can point me to it (because clearly I have missed it) it would also be great.
Thank you in advance,
Mad
Actually I just found out a proper and direct answer to my question. I totally missed it somehow during the last few days of research.
Microsoft's blog has all you need to make it work, and now mine does too. No big explanations and discussions, just basic and direct step by step article.
For those who could not find it and stumbled upon my topic here in StackOverflow, here is the link. Follow it word by word, and it will work.
Answer : Configuring your ASP.NET application for Microsoft OAuth account
I am attempting to write a small, lightweight client, using vb.net winforms, that can install without needing elevated privileges. Before I ask my questions, let me give you a bit of an idea of what it is supposed to do.
The app will start when Windows loads, set like this from the install, with a system/notification tray icon that can be clicked on to load up specific functionality. The application install from a website, or possibly a file share, haven't quite decided yet. This client will initially request user credentials for one of our web programs, and it will talk to an already built web service to determine what functionalities of our services they have licensed access to. After this, credentials will be encrypted and saved to the users pc locally. Every five minutes, the client will pass the credentials to the websites they have access to and check to see the status of jobs that are being processed, and download available reports if needed.
So, here is what I am trying to understand. If I configure this app as a ClickOnce application, once it installs from the url or shared drive, the user will not need to do anything else, correct? Or do they have to visit that url every time they boot up to reinstall/run the client?
Another thing, I wanted to get some opinions on the best ways to do some of the things this app will be doing. I have a good idea of where I am going with it, but I have no idea of which solution to go with yet.
For instance, what is the best way to store user passed credentials on their system for a "remember me"?
Also, is the best way to have the client install with automatically starting on windows startup to configure it to create a shortcut of itself in the windows startup folder?
I am trying to keep this as lightweight as possible, and using a very small GUI, so it shouldn't be too intrusive, so any ideas on how to ensure that, while keeping it from needing admin privs to install, will also help.
If I configure this app as a ClickOnce application, once it installs
from the url or shared drive, the user will not need to do anything
else, correct? Or do they have to visit that url every time they boot
up to reinstall/run the client?
Well if they need to reinstall it, they would have to download the setup.exe file again, but why would users need to do that? CilckOnce supports automatic updates. Visiting url is certainly not needed for running the program.
what is the best way to store user passed credentials on their system
for a "remember me"?
Probably storing them as application settings. Haven't used visual studio 2012, but in visual studio 2010 you have to right-click on project in solutions explorer, go to project propeties and then create variables in Settings tab. Then you can access those variables in code using My.Settings.variableName. Not sure about security though, if you need any.
As for privileges, I think you just need a privilege to install a program. Maybe you should publish a primitive clickOnce application and experiment with it and that will answer all your other questions about clickOnce.
I am finding all sorts of general descriptions of no-touch deployment and lots of questions and problems, but I can't figure how to just get started with it. What is the method that makes it happen? I'm working in VB.Net 2005. I think assembly.loadform will suit me best since I know all of my users and will deploy via my intranet.
Appreciate any links or suggestions for starting places (other than googling "no-touch deployment", I already did that).
If it's a web application project that you're deploying, one-click publish with Web Deploy may be what you're looking for. Here's a related link:
How to: Deploy a Web Application Project Using One-Click Publish and Web Deploy
Apologies if the question is not worded appropriately.
I've created a dashboard using the dashboard designer and succesfully deployed it to our development server. Now I'd like to deploy it to our staging server - is there a way to do that?
I've tried pointing the designer at a different URL without success.
Thanks,
Phil
I ran into same issue and thanks to Umair for reminding me about the import option with the Dashboard Designer. You will open up designer in new location and then use the Import option and point to your ddwx file.
Here is the posting and references from the forum posting - Deploy PPS 2010 dashboard content to new server
I have an additional link in the forum post at the bottom that will send you to the link to the technet documentation as well.
If you only have SSAS reports and SSAS data sources then the PerformancePoint 2010 Content Deployment Tool might be of help.
I have used it to deploy dashboards and reports to another server without issues. It even lets you deploy remotely from dev to other servers if you have the needed permissions. Pretty neat tool, sadly it hasn't been updated recently and still lack a few key features (as the ones I described above).
PPS in SP2013 comes with this built in, but I haven't studied the details yet. Just picked it up from the PPS team in this blogpost
Never figured out a good way to deploy SP lists data connections and SSRS reports though.