DLL Hell a possible solution (repost)

After making some newsgroup postings and researching a bit. I found out some info that might be a contributing factor to our problems with assemblies getting referenced correctly.

In our assemblyinfo file we are auto incrementing the AssemblyVersion . From my reading, this attribute is actually meant to BREAK combatibility. What we need to be using is the AssemblyFileVersion. This can be incremented w/o breaking compatibility and still help us figure out what DLL we are dealing with (which version).

This blog has an entry about it.

Note: I had to repost because I accidently used some tags in my article that don’t show up.

Advertisement

DLL Hell, a possible solution

After making some newsgroup postings and researching a bit. I found out some info that might be a contributing factor to our problems with assemblies getting referenced correctly.

In our assemblyinfo file we are auto incrementing the . From my reading, this attribute is actually meant to BREAK combatibility. What we need to be using is the This can be incremented w/o breaking compatibility and still help us figure out what DLL we are dealing with (which version).

This blog has an entry about it.

.NET DLL Hell

.NET was supposed to resolve the problem of DLL Hell.

Well that is exactly where I am right now: DLL Hell.

I have wasted so much time on stupid versioning issues and other problems that seem to have no cause whatso ever.

Right now I try to build and I get the error:

Cannot copy assembly ‘ASDF.Web.Controls.DateTimeControls’ to file ‘C:DataWalshVSSRootASDF.Web.UsersbinWalshgroup.Web.Controls.DateTimeControls.dll’. The process cannot access the file because it is being used by another process.

Thats nice. No one is using the fricking file, and I haven’t had this problem during my last … oh I don’t know… say …10,000 builds, but now it is becoming an issue. Great.

My other new friend is this error:

The located assembly’s manifest definition with name ‘ASDF.Web.Controls.LookupControl’ does not match the assembly reference.

Thats nice… manually updating the reference, removing it and readding it, rebuilding, manually copying the DLLs to the bin etc don’t help. This is a POS. WTF.

Custom Controls and ASP.NET Validation (Client Side) (MORE)

It turns out that when I said:

It turns out that when I said:
Turns out it is as simple as adding [ValidationPropertyAttribute(“­Text”)] to your class definition for the custom control. That’s easy!
it really wasn’t that easy, at least to get client side support for asp.net validators to work.

After a lot of research, and a bunch of looking through the page output I figured out what must be done.

If you have a custom server control and it is named “MyDateTime1”, then the HTML element that you want to check in your client side validation must also be named “MyDateTime1”. In my control, I would output a bunch of different elemnts, using things like ClientID + “_textbox” and ClientID + “_Icon” etc… All I had to do was make sure the textbox (which is what I wanted to run the client side validation against) was named simply this.ClientID and presto!

It really isn’t that easy.

I think this worked before because I was created HTML elements, and not ASP.NET Webcontrols. I am trying to basically do the same thing, and let me tell you, it isn’t working. I am getting an error saying that there are more than 1 control w/ the same name. The problem (I believe) is that container control is registered w/ asp.net, and when I dynamically add an asp.net textbox with the same name as the parent control, it flips out. With my other control I was just adding an HTML textbox.

Mortgages and Stuff

Just to keep a list of what I am working through here:

I am part way done with the loan process at this place, and they seem to have the lowest price so far (I need to get tax info from Kathleen to complete it). They were 5.375 + 660 closing.

Here is another place I was looking over, those rates are from mtgcapital.com.

I haven’t yet gone through this site.

Here is yahoo’s list of common closing costs.

I haven’t called these guys.