Is there a way to locally host your own Team Foundation Server so that all the machines on a network can work together on the same project?
If so, is there a way to host it so that you can access the TFS outside the network?
I was wondering about this since we are not a lot on the same project and we do not have the money to pay for web hosting. I have a very good machine which would probably be able to run a server.
I'm trying to set up a claims-aware web app development environment. I am new to ADFS 2.0 and ultimately, I want to be able to authenticate against two different domains. I think I am very close but I'm getting a certificate error from one of the ADFS servers.
During processing of the Federation Service configuration, the element 'serviceIdentityToken' was found to have invalid data. The private key for the certificate that was configured could not be accessed.
This error is recorded in the ADFS server event log on domain #1 after I enter credentials in the web app. Even with working credentials, I get passed to a 401 unauthorized access page.
The user account running the ADFS service has permissions to the private key of the certificate so I am not sure why I am getting this error.
What I have done so far:
I also haven't set up a Relying Party Trust on either of the ADFS servers. Is this necessary? I can't seem to find any good documentation explaining how this is supposed to work.
I have followed this ( http://blogs.msdn.com/b/alextch/archive/2011/06/27/building-a-test-claims-aware-asp-net-application-and-integrating-it-with-adfs-2-0-security-token-service-sts.aspx ) guide in setting this up, but I feel like there is probably a simple step I have missed somewhere.
To summarize:
Thanks in advance for any help on this. Someone who is familiar with ADFS could probably set this up in matter of minutes!
Let's say I have a simple web page with svg image in it:
<img src="foobar.svg" alt="not working" />
If I make this page as static html page and view it directly svg is displayed. If I type the address of this svg -- it is displayed.
But when I make this as .aspx page and launch it dynamically from Visual Studio I get alt text. If I type the address of this svg (from localhost, not as a local file) -- browser tries to download it instead of displaying.
I already defined mime type in IIS (for entire server -- "image/svg+xml") and restarted IIS. Same effect as before.
Question: what should I do more?
WireShark won't work (it is in documentation), I tried also RawCap, but it cannot trace my connection (odd), luckily Fiddler worked:
From client:
GET http://127.0.0.1:1731/svg/document_edit.svg HTTP/1.1
Host: 127.0.0.1:1731
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.1) Gecko/20100101 Firefox/10.0.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Answer from server:
HTTP/1.1 200 OK
Server: ASP.NET Development Server/10.0.0.0
Date: Thu, 16 Feb 2012 11:14:38 GMT
X-AspNet-Version: 4.0.30319
Cache-Control: private
Content-Type: application/octet-stream
Content-Length: 87924
Connection: Close
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- Created with Inkscape (http://www.inkscape.org/) -->
<svg
xmlns:
*** FIDDLER: RawDisplay truncated at 128 characters. Right-click to disable truncation. ***
For the record, here is useful Q&A for Fiddler: https://stackoverflow.com/questions/826134/how-to-display-localhost-traffic-in-fiddler-while-debugging-an-asp-net-applicati
i have the local developement machine (win 7) with iis 7.5.7600 and i can deploy a website from .zip file that was generated with visual studio 2010 using "Import Application..." link in an iis website
However the win 2008 r2 server that has same iis version doesn't have "Import Application..." link, it only has "add application from gallery"
the question is how do i deploy it on the server?
***removed secondary question****
using framework 4
We are trying to simplify the publishing process by utilizing Web Deploy through VS2010. We want to be able to quickly rollback any broken releases, so we create folders for each release:
As of now, I publish the site locally, copy the files to the new release folder on our server, and then manually update the site's physical path to the new folder in IIS. Because the site points to a specific release's folder, I am unable to use web deploy on that site as the result would overwrite the existing files.
My solution to the overwrite problem was to create a deployment site that points to root folder (C:\www) and use web deploy to create the new release. The next step is to update the physical path of the site, but I'm unable to find a proper way to accomplish this. I'm aware of executing a command in the post-build event, but I'm getting a little lost with the web deploy documentation since the verb options are to sync, dump and delete.
When the publish is complete, I just need the IIS site to point to the new physical path. Is this possible? I'm open to alternative options (like publish locally then execute a batch file).