I wanted to do a tech.ed talk on ESE but it was rejectedah, what might
have been.
Ah! The pillocks.
Anyway, I've read the samples, some of the source code and some of the
documentation and I think they CodePlex team have done a really neat job on
wrapping esent.dll in a friendly way tha
On Sun, Aug 8, 2010 at 5:23 PM, Greg Keogh wrote:
[...]
> I am quite sure that I will use managed ESENT in real apps quite soon. Like
> UDP and T4, I reckon it’s one of those hidden gems.
What is UDP? Or are you referring to the protocol?
> Greg
--
silky
http://dnoondt.wordpress.com/
"Eve
I'm needing to debug a Windows service to see why it is crashing after a few
minutes.
I've setup the remote debugger on the host machine, but I receive the error
message "Unable to connect to the Microsoft Visual Studio Remote Debugging
Monitor named 'x'. Logon Failure: unknown username or bad pass
Have you tried logging on with credentials from the remote computer?
ie, create a local "testuser" account on the remote server and log on
with "remoteserver\testuser".
Is the trace option turned off in the app.config?
David
"If we can hit that bullseye, the rest of the dominoes
will fall like a
> Is the trace option turned off in the app.config?
Do you mean have I setup the system.diagnostics section; then yes I have as
below. I haven't however used the trace options which are part of system.web
as I'm sure you don't need these in a windows service, please correct me
though if I am wrong
No luck. Same result.
Liked the idea though.
I also made sure that the user was in the VS remote debugger permissions and
they had debugging permissions under the local security policies.
-
Michael Lyons
-Original Message-
From: Ken Schaefer [mailto:k...@adopenstatic.com]
S
Guys,
I have created 3 permanent full time positions in sunny Brisbane: 1 x
Team Lead, 2 x Analyst/Developers
Required:
- Extensive experience in C#.Net Winforms (3.5)
- Experience in SQL 2005/2008
- Experience in fully SDLC, inc Business Requirement Analysis
- Strong customer focus
- High perfor
Hi all,
I am currently trying to improve the template code in our stored proc
generator.
In the insert stored proc, there seems to be a lot of code with references to
deadlock detection,
and attempts to re-run the insert if it fails due to a deadlock.
But the insert statement itself has a RO
Tony
Something I've seen several times:
The table doesn't have a trigger to update the row with a datetime stamp
on row insert/modify.
Simon
On 9/08/2010 9:47 AM, ton...@tpg.com.au wrote:
Hi all,
I am currently trying to improve the template code in our stored proc generator.
In the insert
If you are still stuck then I would give windbg a try (see earlier post '
Unable to diagnose a crash') as it may be able to give you enough info to
fix the problem
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Michael Lyons
Sent:
S close. I can see that it logged on the remote host with the same
username, but now it's spewing out another error.
"Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor
names 'x'. The Visual Studio Remote Debugger on the target computer cannot
connect back to this comput
Windows (or any other) firewall maybe?
David
"If we can hit that bullseye, the rest of the dominoes
will fall like a house of cards... checkmate!"
-Zapp Brannigan, Futurama
On Mon, Aug 9, 2010 at 10:50, Michael Lyons wrote:
> S close. I can see that it logged on the remote host with the
I've used windbg before with crash dumps and I can even use the 'Problem
reports and solutions' section under control panel to kind of see where the
error is happening. But under test conditions this seems to work fine. I'm
sure it's something to do with specific machine and particular function
par
I've turned both off with no firewalls in between. :(
-
Michael Lyons
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of David Richards
Sent: Monday, 9 August 2010 10:53 AM
To: ozDotNet
Subject: Re: Remote debugging outsi
If I was in this position, I would install VS on a notebook (if you don't have
one spare, they are pretty cheap these days) and place it in the same network
environment as your server.
I would then use remote debugging to discover the issue and if necessary nuke
the notebook afterwards.
>From
Hi all,
According to:
https://connect.microsoft.com/SQLServer/feedback/details/328811/scope-identity-sometimes-
returns-incorrect-value
SCOPE_IDENTITY() has a bug that causes it to fail whenever parallelism kicks in
(a more common
occurence these days with the proliferation of multiprocessor
"Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor
names 'x'. The Visual Studio Remote Debugger on the target computer cannot
connect back to this computer. Authentication failed. Please see Help for
assistance."
Hi Michael, my condolences. I spent many solid hours of suffe
Condolences++
Why do you make it so damn hard to debug a process on a remote machine
(listen up Microsoft)
As always, I'm sure there is a good reason for everything but this is what
would be nice:
a) you install remote debugging on remote machine
b) you forward port on firewall (optionally)
c) e
Hi all,
I have my archidev hat on at the moment (given my last few emails I'm betting
that doesn't
surprise people)
One task I have been looking at is figuring out how to convert our applications
from Linq to SQL
over to Linq to Entities. The reasons are that Linq to Entities is installed
ou
I previously had it working once before on another project, but that was
before we put our workstations into a domain and it was a slight challenge
for 30 minutes, but then all ran smoothly.
The notebook idea isn't a bad idea, but it's not really an ideal long term
solution.
Would be nice if there
I have to say it would be really nice if it just worked similar to what you
were saying but popped up with an authentication dialog where you could
actually logon remotely using the debugging account.
-
Michael Lyons
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mail
It's probably bad security, (but if you're inside a LAN or connecting via
VPN or SSH it likely doesn't matter) but have you tried going to the options
dialog (inside remote debugger stub) and tick allow any user to debug?
On 8 August 2010 20:02, Michael Lyons wrote:
> I'm needing to debug a Wind
I totally agree with you Tony. I've always felt the LINQ to SQL designer was
somewhat more thought out and aimed at the whole KISS principle, while LINQ
to Entities tried to be "enterprisey" when it really didn't need to be.
Admittedly I haven't taken a look at EF since back when it first came out
Yes I have tried that and unfortunately it’s only native which means I lose the
ability to set break points as it doesn’t recognise the PDB’s.
-
Michael Lyons
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of mike smith
Sent: Monday, 9
Yea but you could always use First, right? Single would only be fractionally
faster, if at all,
methinks..
On Mon, Aug 9th, 2010 at 1:30 PM, Michael Lyons wrote:
> I totally agree with you Tony. I've always felt the LINQ to SQL designer
> was
> somewhat more thought out and aimed at the whole
Coincidently I spoke to the PM on this feature last week about this very issue.
It's a known limitation - which requires a re-architecture of the remote
debugging engine. Unfortunately, you won't see this supported until a future
version of VS.
-Original Message-
From: ozdotnet-boun...@
First should be quicker than Single shouldn't it? First just has to find one
result. Single has to find all results and ensure there is only one.
Michael M. Minutillo
Indiscriminate Information Sponge
Blog: http://wolfbyte-net.blogspot.com
On Mon, Aug 9, 2010 at 12:10 PM, wrote:
> Yea but yo
Single() shouldn't have to find all results, it just has to check if
there is more than one.
On Mon, Aug 9, 2010 at 2:49 PM, Michael Minutillo
wrote:
> First should be quicker than Single shouldn't it? First just has to find one
> result. Single has to find all results and ensure there is only on
I'm guessing windbg gives you the same problems? In some respects it's
better than remotedebugger and VisualStudio
On 9 August 2010 13:35, Michael Lyons wrote:
> Yes I have tried that and unfortunately it’s only native which means I
> lose the ability to set break points as it doesn’t recognis
29 matches
Mail list logo
