Activity overview
Latest activity by raffaeu
Report Errors without recompiling my assemblies
Hello everybody, we are heavily using SA error reporting feature in our projects and so far we were able to accomplish this task just by recompiling the assembly (.exe or .dll) using the SA MsBuild...
Ok Brian, I didn't know.
I will make a test with the SDK because probably it's the best way to go.
Thank you again for your support, really appreciated! [image] / comments
Ok Brian, I didn't know.
I will make a test with the SDK because probably it's the best way to go.
Thank you again for your support, really appreciated!
That really fixed my problem. [image] / comments
That really fixed my problem.
If we have hundreds of machines in our network and one of them was reporting an error how would we determine which one of them was reporting the error? / comments
If we have hundreds of machines in our network and one of them was reporting an error how would we determine which one of them was reporting the error?
Just to let you know, I got this problem fixed with the following technique.
This is my project structure in Visual Studio
+ Solution Dir
+ UI Project (ClickOnce)
+ Domain project (.dll)
+ Data Layer project (.dll)
+ Service project (.dll)
- .saprj file (in the root)
This is my .saprj file where I specify to TFS how to resolve dynamically the dependencies:
<Assembly AssemblyName="TestSA.DataLayer, Culture=neutral, PublicKeyToken=null" MandatoryPath=".\TestSA.DataLayer\obj\Release\TestSA.DataLayer.dll">
<Merging />
<Embedding />
</Assembly>
<Assembly AssemblyName="TestSA.Domain, Culture=neutral, PublicKeyToken=null" MandatoryPath=".\TestSA.Domain\obj\Release\TestSA.Domain.dll">
<Merging />
<Embedding />
</Assembly>
<Assembly AssemblyName="TestSA.ServiceLayer, Culture=neutral, PublicKeyToken=null" MandatoryPath="TestSA.ServiceLayer\obj\Release\TestSA.ServiceLayer.dll">
<Merging />
<Embedding />
</Assembly>
In this way I have a dynamic way of structuring my solution in TFS without the need to touch anything except the saprj file! [image]
PS: I hope this may help somebody else too. / comments
Just to let you know, I got this problem fixed with the following technique.
This is my project structure in Visual Studio
+ Solution Dir
+ UI Project (ClickOnce)
+ Domain project ...
Assembly dependencies and MsBuild task
Hi everybody, I have sucesfully used your MsBuild task on multiple projects until the project does not have references to external .dlls
Right now I have the following application structure:
- Solu...
Feature request
Hello guys, we have a particular feature request and we are wondering to know if it is possible to get it in the next release.
In the session table you report two fields, UserID and UserHostAddress...
That make sense now. [image] / comments
That make sense now.
That's really interesting, I didn't find before.
THank you! / comments
That's really interesting, I didn't find before.
THank you!
That's very easy to explain.
We have various ClickOnce applications and we have a three tier deployment infrastructure: dev.local, qa.com and production.com on three different domains.
Our plan is to release a version for dev.local that will report to a specific SQL/web server and then if it's working we will re-publish using qa and so on ...
Using your approach we need 3 different physical TFS build server with three different licenses of SA configured for the three environments.
Right now we solved the issue using DNS rules so that the three web server and the three SA SQL server are recognized using the same DNS name.
We have decided to use your windows form application provided with the SDK and translate it into a Silverlight application that will allow us to create also tasks in TFS. / comments
That's very easy to explain.
We have various ClickOnce applications and we have a three tier deployment infrastructure: dev.local, qa.com and production.com on three different domains.
Our plan is ...