Source sample site port conflicts with build sample sites?

[Richard Collette]

I am working with both the source project and the built library including its samples.  When you open the source solution, it wants to create the sample site virtual directories in IIS locally, whereas the build library samples will run in the development server.

So if I let the source solution create the virtual directories, I can no longer run/launch the build sample sites due to port conflicts.

There's probably a simple way around this so I am wondering what anyone else is doing when working with both the source and build sample sites?   The only thing I can think of is to shut down my local IIS when working with the build samples.  Is that what others are doing?

Thank you,
Rich

[Andrew Arnott]

Are you running the built v4.0.x version of the library while working with the source code from the master branch?  If so, that's probably what's causing the conflicts.  You may want to work out of the v4.0 branch in source control so that they all are configured to use the same web server settings.

As an aside, the use of IIS Express in the master branch is probably going to be reverted.  It has proven to be problematic.
--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre

--
You received this message because you are subscribed to the Google Groups "DotNetOpenAuth" group.
To view this discussion on the web visit https://groups.google.com/d/msg/dotnetopenid/-/VD1l5YQKWjwJ.
To post to this group, send email to dotnet...@googlegroups.com.
To unsubscribe from this group, send email to dotnetopenid...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dotnetopenid?hl=en.