I am using with aspnet_merge as well I did not have problems with that.
One thing that concerns me is that you said "we don't merge until
deployment". Not sure what you mean exactly but for me merging is part of
deployment.
First I develop a project on my machine then when it's ready I compile it
with aspnet_compiler.exe and then merge it with aspnet_merge.exe
And then move it to production.
-----------------------------------------
Also some good point i read recently is if you have 2 pages with the same
name in different folders merge will fail.
read more here
http://www.cosmocentral.com/post/MSB...th-Code-1.aspx
and here
http://www.dotnet2themax.com/blogs/m...ab0f34d4e.aspx
George.
"tbh" <fe****@newsgroups.nospamwrote in message
news:uQ*************@TK2MSFTNGP06.phx.gbl...
hi,
off and on i have run into troubles with aspnet_merge. since these
problems don't appear on my development machine (we don't merge until
deployment) they are time-consuming and annoying.
i've searched for clues here and elsewhere but haven't found much
definitive yet. in particular, is there a newer version of aspnet_merge
that doesn't (nearly) crash with the unhelpful message:
An error occurred when merging assemblies: Der Objektverweis wurde
nicht auf eine Objektinstanz festgelegt.
(the German means roughly null reference exception error)
?
if we had some clues about what was referencing what, the tool would be
considerably more useful.
cheers,
Tim Hanson