We're not using Team edition, we're subversion based. So I just created
the directory in explorer and added it to SVN. The VS solution knows
nothing about the directory, and the individual projects just reference
the DLLs directly from the directory with copy-local set to yes.
-Walden
--
Walden, so you create a directory at the Solution level? Right-click solution
-> Add -> New solution folder? Name it Binaries. Then right-click on the newly
added Binaries folder and select Add-> New Item and select the log4net .dll
(release version) ? from the path it was installed when I do
What you describe vis-a-vie the build process is indeed the difference
between a file reference and a project reference. The two nice things
about a project reference is that when you build debug you reference the
debug version of the other project, but when you build release you
reference the rele
Great! Now comes the question, what about project reference vs. file
reference? MSDN recommends using project references whenever possible and only
use file references when necessary.
I haven’t been using .Net that long and I’m still a little fuzzy on all the
setup choices. We’re on VS2005
This is exactly right. The only downside of deploying unsigned log4net with
each application is that you would end up with a copy of the dll in each
deployed application. At < 300k that is a very small downside in most
situations.
Jim
From: Walden H. Leverich [mailto:[EMAIL PROTECTED]
Sent:
> just want to be able to go into each project and add a reference to
the log4net.dll and that should do it.
>No GAC just a reference in each project to the log4net.dll.
Correct. _IF_ you used the signed version (or signed a build yourself)
you could drop it in the GAC and then you wouldn't
Yes, just reference the dll in your project and include it with the app when
you deploy.
From: hdjim69 [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 30, 2008 10:04 AM
To: Log4NET User
Subject: RE: when to use strong name confusion
Yes, this is for internal use. We are not a vendor. However
Yes, this is for internal use. We are not a vendor. However we have several
projects in the solution (VS2005) that need to log (client.exe, client.dll,
server.dll, etc.). I just want to be able to go into each project and add a
reference to the log4net.dll and that should do it. No GAC just a
The only change I made was this:
I included a Global.asax file to my web service, and wrote the following
line of code in the start method. That is it ... the code worked and the
logging happened.
***
void Application_Start(object sender, EventArgs e)
Is this for _internal_ use? IOW, you're not a ISV getting ready to
distribute software, right? In that case, just ignore strong names
completely. Use the DLL as it, and don't worry about sn.exe or signing
at all. Except in rare cases (and you'll know when you get there) there
is no point in using s
This is likely a permissions error. You need to grant the ASP.NET user (or
NETWORK SERVICE user for Win2k3 or higher) write permissions on the folder
where you want to write the log file to. The default is to only allow the
user to read files, not write them.
-Original Message-
From: Sri
Hello,
Not sure I understand the strong name requirements. I'm on .Net 2.0. There is
already a .dll in the log4net-1.2.10\bin\net\2.0 dir. Do I need to rebuild this
.dll with a strong name key or can I just use this dll as it is ? I know
what a strong name is and how to generate a privat
My web service is using C# and .Net 2.0
When a "handled" exception is thrown during the web service call, the
service should return normally but should log some information so some admin
chappie can look at it later.
So I thought of usnig log4net but don't know how to. After checking on the
net,
13 matches
Mail list logo
