1 comments
.NET 
If you don't know what I am referring to in the title of this blogpost, read my previous post first.
Mike wrote a follow-up on his upgrade guide for TFS v1 to WSS v3, and this time it's a lot better because (for starters) it doesn't involve hacking into the process template. Read his update here -> click
Two remarks spring to mind:
1. Sorry you refer to my blogpost as a negative reaction, Mike. It wasn't meant as a flame or something, just a critical view on what you were trying to do. Given the fact you wrote a follow-up, I think I (and the others with critical comments) proved our point what was wrong with it in the first place.
2. You are talking about raising the trust level for the WSS virtual website. You need to do this because you deploy your new asmx into the bin folder of this website. If you deploy it into the GAC it should not, in theory, be necessary to raise the trust level.
One comment
Bart,
Sorry that it seems now your response looked negative. It was indeed not positive, but luckily there are also people who will keep you focused. This way I took the liberty to search for the real problem, without changing the Process Template.
Thnx again,
Mike
Ps. Good advice for putting it in the GAC. I’ll mention it in my blog.
Mike Glaser