Change Web Service Location

.NET obfuscator and automated error reporting

Moderators: Luke Jefferson, melvyn.harbour, dom.smith

Change Web Service Location

Postby lee5i3 » Mon Mar 07, 2011 8:51 pm

Is it possible to change the web service location without having to republish?

Here is why, I'd like to have more than one web server, that way I know if test/staging or production is getting the errors rather than having them all at same location.

However I don't want to have to have different DLLs, rather have a setting or even allow a way to set the web service location in code.
lee5i3
 
Posts: 38
Joined: Fri Jul 16, 2010 9:26 pm

Postby craigm » Wed Mar 09, 2011 12:00 am

We send our error reports to different email address which are all forwarded to our developers. e.g. Our beta program sends errors to beta.programname.errors@company.com and production to programname.errors@company.com. They all redirect to errors@company.com, but we can see who the email was originally sent to. You could also change the product name if you want the errors to be grouped differently within the Smart Assembly error repository.
craigm
 
Posts: 9
Joined: Wed Jun 23, 2010 1:13 pm

Postby Brian Donahue » Wed Mar 09, 2011 11:24 am

It looks to me like SmartAssembly puts the webservice address in at build-time, so you can 't change it. You would need different SA options set for your release and debug builds, specifying a different webservice.

It may be easier just to make different projects for test and release, using different project names, that way you could tell release error reports from testing error reports.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby lee5i3 » Thu Mar 10, 2011 4:08 pm

That will be a showstopper for our applications due to our process flow.

Builds are compiled on our developer machines, each compile is sent to testing, then to staging, then to production.

(We currently only have 1 copy due to cost, so I'm only developer using this and I'm still pushing our administration to use a build server so we can use dev licenses, but we are limited due to our source control (Vault), which doesn't support many build servers that I've found)

So we would need a single web server, which is unlikely possible to be approved.

The reason for this is, each compile may or may not have bug fixes, can't 100% guarantee that what compile will not fail testing.

I will just wait to see if you guys implement a way to dynamically set the URL.
lee5i3
 
Posts: 38
Joined: Fri Jul 16, 2010 9:26 pm

Postby Robert » Thu Mar 10, 2011 5:36 pm

As a largely off-topic reply (nothing to do with SA - I've leave you in Brian's capable hands there!), we used to use Vault at Red Gate, and CruiseControl.NET seemed to talk to it nicely. There's a CC.NET plug-in on the SourceGear site: <http://www.sourcegear.com/downloads.html>

I'm not sure CC.NET is particularly actively maintained nowadays, but it's served us relatively well in the past, with a few tweaks here and there!

Hope that helps!
Rob
Robert Chipperfield
Red Gate
Robert
 
Posts: 410
Joined: Mon Oct 30, 2006 11:15 am
Location: Cambridge, UK

Postby lee5i3 » Thu Mar 10, 2011 8:05 pm

We are considering moving to TFS 2010, once I can get my DBA to open up permission for it! lol


I will keep track of SA changes in the future, I still will be using it for obfuscation, however the error reporting will need to wait till its more dynamic with our system.
lee5i3
 
Posts: 38
Joined: Fri Jul 16, 2010 9:26 pm


Return to SmartAssembly 6

Who is online

Users browsing this forum: onnb and 0 guests