Recompilling builds OLD code???

[Programmer]

I'm at my witts end! I've written a Windows service using VS.NET 2K3. It's a service that is basically a TcpListener. When I telnet to it, the text responses the service gives back are not even in my source code... I removed them days ago. I've done the obvious like:

- searched all my local drives for the binaries and deleted them.
- deleted the bin and obj folders from the main project folder and the setup folder.
- I even did a search (both 8-bit and Unicode) search on ALL files on ALL of my drives for the existence of the old strings and found nothing. (I used Visual SlickEdit's search, not Windows XP Pro's search).
- Ensured the service exe wasn't cached in the Windows cache folders.

But every time I build the exe and the setup, then install and test, it's STILL producing the old strings. I am totally baffled.

OS = WinXP Pro
Dev = VS.NET 2K3
Using SourceSafe 6.0c (Build 9447) (and I checked the version in source safe... also does not have the old strings).

I'm hoping I've just overlooked something really simple, but I think I've got my bases covered here. Any ideas?

 

[Paul Lyons]

Hi

I remember we were having similar issues some time back
that we fixed. My memory is not 100% on how we fixed it,
but I think using InstallUtil to unistall the service and
reinstall the new version was involved.
Either that or the GAC had a copy, but you seem to have
eliminated that probablity..?

HTH..Paul

-----Original Message-----
I'm at my witts end! I've written a Windows service

using VS.NET 2K3. It's a service that is basically a
TcpListener. When I telnet to it, the text responses the
service gives back are not even in my source code... I
removed them days ago. I've done the obvious like:

- searched all my local drives for the binaries and deleted them.
- deleted the bin and obj folders from the main project folder and the setup folder.
- I even did a search (both 8-bit and Unicode) search on

ALL files on ALL of my drives for the existence of the
old strings and found nothing. (I used Visual SlickEdit's
search, not Windows XP Pro's search).

- Ensured the service exe wasn't cached in the Windows cache folders.

But every time I build the exe and the setup, then

install and test, it's STILL producing the old strings.
I am totally baffled.

OS = WinXP Pro
Dev = VS.NET 2K3
Using SourceSafe 6.0c (Build 9447) (and I checked the

version in source safe... also does not have the old
strings).

I'm hoping I've just overlooked something really simple,

but I think I've got my bases covered here. Any ideas?

 

[Charles Law]

Hi Programmer

I don't know if this could be the cause of your problem, but I had a similar
situation recently in a Windows forms app. I tracked it down to the
references that VS keeps. Go to Project / Application Properties / Common
Properties / Reference Path. Have a look in the Reference Path list and
remove any that are incorrect. I had a long list as I had moved the project
directory a couple of times.

HTH

Charles


I'm at my witts end! I've written a Windows service using VS.NET 2K3. It's
a service that is basically a TcpListener. When I telnet to it, the text
responses the service gives back are not even in my source code... I removed
them days ago. I've done the obvious like:

- searched all my local drives for the binaries and deleted them.
- deleted the bin and obj folders from the main project folder and the setup
folder.
- I even did a search (both 8-bit and Unicode) search on ALL files on ALL of
my drives for the existence of the old strings and found nothing. (I used
Visual SlickEdit's search, not Windows XP Pro's search).
- Ensured the service exe wasn't cached in the Windows cache folders.

But every time I build the exe and the setup, then install and test, it's
STILL producing the old strings. I am totally baffled.

OS = WinXP Pro
Dev = VS.NET 2K3
Using SourceSafe 6.0c (Build 9447) (and I checked the version in source
safe... also does not have the old strings).

I'm hoping I've just overlooked something really simple, but I think I've
got my bases covered here. Any ideas?

 

[Programmer]

Yes. Unfortunately.

Here's some more info:

What I'm writing is a customized SMTP server. When I change the text of the
initial response string, it's always OK. But the text from the QUIT command
always says, "221 Closing connection. Good bye." That text is no longer in
my source code. I've even added several other lines of text to output upon
the QUIT command, but they don't show up. I can even debug it and step
through the new lines of code. They execute, but strangely, the output of
the QUIT command is as if it's running a week-old version.

One of my initial thoughts was that I was still running the Microsoft SMTP
server, but I'm not. I've shut it down and everything else about the
running SMTP server on port 25 is my stuff.

It's just supre strange. I would never believe anyone telling me this
unless I saw it for myself.

Thanks

 

[Jon Skeet]

Yes. Unfortunately.

Here's some more info:

What I'm writing is a customized SMTP server. When I change the text of the
initial response string, it's always OK. But the text from the QUIT command
always says, "221 Closing connection. Good bye." That text is no longer in
my source code. I've even added several other lines of text to output upon
the QUIT command, but they don't show up. I can even debug it and step
through the new lines of code. They execute, but strangely, the output of
the QUIT command is as if it's running a week-old version.

One of my initial thoughts was that I was still running the Microsoft SMTP
server, but I'm not. I've shut it down and everything else about the
running SMTP server on port 25 is my stuff.

It's just supre strange. I would never believe anyone telling me this
unless I saw it for myself.

I suggest you examine the assembly with ILDASM - that should show you a
bit more information. Have a look at where the QUIT text is coming from
- and preferrably, make a change in that method and see whether the IL
changes at all.