Sounds you need a 'well known store' of information that would indicate
what code is available, where it is what version it is, etc...
Some central xml file that clients know the location of.
Or, a webservice that returns this info to the caller, or, client machines
just enumerate a directory stru
Hi Claus, is it possible for you to create a serviced component as a wrapper
for your .Net app-- hopefully your application are some DLLs. Then the only
thing need to be done is to create the Interop and distributed to any client
app, no matter .Net or legacy.
If your interface doesn't changes oft
At 04:23 PM 1/8/2004, Claus Brod wrote
>Brandon Manchester wrote:
>>In your client's app.config file you can add an section
>>that can specify things like binding redirects (for versioning), codebases,
>>and probing information.
>
>True, but that would require changes in the config files of all cl
I'm pretty sure you're out of luck and that things just won't work the way
you're wanting. The GAC is there for a reason - so people can bind to your
assembly no matter where they are. Probing path configuration changes in the
client won't work as they require subdirectories and not absolute
direct
Brandon Manchester wrote:
In your client's app.config file you can add an section
that can specify things like binding redirects (for versioning), codebases,
and probing information.
True, but that would require changes in the config files of all clients,
wouldn't it? Our application doesn't neces
Don't know if this is what your after or not but here goes...
In your client's app.config file you can add an section
that can specify things like binding redirects (for versioning), codebases,
and probing information.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
I'd think you should be writing "stub" routines for your eventual "perform some bit of
database work using these parameters, examine the result(s), return info to app or
raise an exception" routines, (Such routines don't always have to be implemented by
calling SPs.) Those "stub" routines shou
Here is a link to a mock object project for .net data providers
http://sourceforge.net/projects/dotnetmock/
The real key to this though, if you want to test your code that uses database
access is how to inject the test data. With a separate test database, you have
only to change connection strin
SteveC said:
> My development cycle typically includes tiered coders, each are given an
> explicit document of "what to do", even in calling stored procedures.
> The problem is that all of the stored procedures are not ready or
> written (or sometimes fully thought out and need to be changed) on th
I did try a loop similar to what you described (at the suggestion of another
poster). Everything took longer yesterday since I was running it over a DSL
connection (VPN into work), but things took longer with just the property
references than they did with property references and row operations.
>
> As the spawning process, you should be able to do something like so:
>
[snip 7 step process]
BTW - if you're only interested in knowing that the child process exited,
but don't need to distinguish between a normal exit and an abnormal one due
to an unhandled exception, then you can omit steps
No, because MSDE would require me to install the database and start to write
TSQL. I don't want to do that. I am thinking about a .NET assembly that
will pretend that it is a real database and return a TDS stream, while it is
actually not. Something that would listen on the actual SQL server por
Thanks for the tip.
The (dangling?) reference appears not to have been removed by the windows
installer when the package was uninstalled. I suspect that this is somehow
related to the fact that I had previously installed the assembly into the
GAC on the same machine using gacutil. I built a deplom
Works like a charm - thanks
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] Behalf Of Paul Ceccato
Sent: 08 January 2004 12:25
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Removing a referenced assembly from the
GAC
The GAC is impl
14 matches
Mail list logo
