|
He could a) strongly name them (detects rogue replacement), and then b) run an obfuscator on them. Most of the commercial obfuscators can merge assemblies, encrypt strings, and create native Windows binaries, so that would solve the decompile problem.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Christian Graus wrote: Don't do that.
reason ?
Christian Graus wrote: They can always decompile yours, anyhow, so you've lost that battle before you start.
nono, i dont scare of decompile. I know noone can prevent their dlls or exes. All i just want to hide the dlls, my app should look like single exe app. thats it.
TVMU^P[[IGIOQHG^JSH`A#@`RFJ\c^JPL>;"[,*/|+&WLEZGc`AFXc!L
%^]*IRXD#@GKCQ`R\^SF_WcHbORY87֦ʻ6ϣN8ȤBcRAV\Z^&SU~%CSWQ@#2
W_AD`EPABIKRDFVS)EVLQK)JKSQXUFYK[M`UKs*$GwU#(QDXBER@CBN%
Rs0~53%eYrd8mt^7Z6]iTF+(EWfJ9zaK-iTV.C\y<pjxsg-b$f4ia>
--------------------------------------------------------
128 bit encrypted signature, crack if you can
|
|
|
|
|
Xmen wrote: All i just want to hide the dlls, my app should look like single exe app. thats it.
The best way to do that is to merge the assemblies.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
John Simmons / outlaw programmer wrote: merge the assemblies.
hehe how simply you said that, any way ? 
TVMU^P[[IGIOQHG^JSH`A#@`RFJ\c^JPL>;"[,*/|+&WLEZGc`AFXc!L
%^]*IRXD#@GKCQ`R\^SF_WcHbORY87֦ʻ6ϣN8ȤBcRAV\Z^&SU~%CSWQ@#2
W_AD`EPABIKRDFVS)EVLQK)JKSQXUFYK[M`UKs*$GwU#(QDXBER@CBN%
Rs0~53%eYrd8mt^7Z6]iTF+(EWfJ9zaK-iTV.C\y<pjxsg-b$f4ia>
--------------------------------------------------------
128 bit encrypted signature, crack if you can
|
|
|
|
|
You can use IlMerge[^] to merge managed assemblies.
|
|
|
|
|
yupp mate, i tried that too but that thing is very typical. After spending hrs on that i had nothing new 
TVMU^P[[IGIOQHG^JSH`A#@`RFJ\c^JPL>;"[,*/|+&WLEZGc`AFXc!L
%^]*IRXD#@GKCQ`R\^SF_WcHbORY87֦ʻ6ϣN8ȤBcRAV\Z^&SU~%CSWQ@#2
W_AD`EPABIKRDFVS)EVLQK)JKSQXUFYK[M`UKs*$GwU#(QDXBER@CBN%
Rs0~53%eYrd8mt^7Z6]iTF+(EWfJ9zaK-iTV.C\y<pjxsg-b$f4ia>
--------------------------------------------------------
128 bit encrypted signature, crack if you can
|
|
|
|
|
Because one feature of .NET is meant to be that you can copy a folder and move it to another machine to redeploy. Also, because those folders get polluted with too much crap and it's better not to contribute. Finally, if some other app has a dll with the same name as yours and they go to the same place, what happens then ? Oh, if you have to release more than one version of the sale dll, putting them in the app folder means you can safely do that.
Christian Graus
Driven to the arms of OSX by Vista.
|
|
|
|
|
yeah i agree with you but dude understand this situation...this is different, no connection with any rule or anything. E.g. a best friend of you that says to you to make an app for him/her and (s)he says also that app must be single exe then what will you do. Wont you develope one ? Will you say him/her that this is poor design ?
TVMU^P[[IGIOQHG^JSH`A#@`RFJ\c^JPL>;"[,*/|+&WLEZGc`AFXc!L
%^]*IRXD#@GKCQ`R\^SF_WcHbORY87֦ʻ6ϣN8ȤBcRAV\Z^&SU~%CSWQ@#2
W_AD`EPABIKRDFVS)EVLQK)JKSQXUFYK[M`UKs*$GwU#(QDXBER@CBN%
Rs0~53%eYrd8mt^7Z6]iTF+(EWfJ9zaK-iTV.C\y<pjxsg-b$f4ia>
--------------------------------------------------------
128 bit encrypted signature, crack if you can
|
|
|
|
|
If you place dlls in other directory, you can use Appdomain.AssemblyResolve event to point your application to the dll it needs. But as everyone can look into your application, they will be able to see the directory where the dlls reside.
|
|
|
|
|
Giorgi Dalakishvili wrote: But as everyone can look into your application, they will be able to see the directory where the dlls reside.
yes, thats biggest drawback of .net applications
anyway i have to do what i need  i will try Appdomain.AssemblyResolve
TVMU^P[[IGIOQHG^JSH`A#@`RFJ\c^JPL>;"[,*/|+&WLEZGc`AFXc!L
%^]*IRXD#@GKCQ`R\^SF_WcHbORY87֦ʻ6ϣN8ȤBcRAV\Z^&SU~%CSWQ@#2
W_AD`EPABIKRDFVS)EVLQK)JKSQXUFYK[M`UKs*$GwU#(QDXBER@CBN%
Rs0~53%eYrd8mt^7Z6]iTF+(EWfJ9zaK-iTV.C\y<pjxsg-b$f4ia>
--------------------------------------------------------
128 bit encrypted signature, crack if you can
|
|
|
|
|
If you strongly name the assemblies and install into the GAC you won't need to go to this trouble.
You could also use the config file to tell where your assemblies are located
Assembly Placement[^]
You may also want to review this article How the Runtime Locates Assemblies[^]
Moving assemblies around just so your app appears as a single file is a poor design and deployment choice anyway.
only two letters away from being an asset
|
|
|
|
|
Mark Nischalke wrote: Moving assemblies around just so your app appears as a single file is a poor design
yes i know, but im not gonna sell it or noone gonna purchase it. Its for someone else, someone special.
TVMU^P[[IGIOQHG^JSH`A#@`RFJ\c^JPL>;"[,*/|+&WLEZGc`AFXc!L
%^]*IRXD#@GKCQ`R\^SF_WcHbORY87֦ʻ6ϣN8ȤBcRAV\Z^&SU~%CSWQ@#2
W_AD`EPABIKRDFVS)EVLQK)JKSQXUFYK[M`UKs*$GwU#(QDXBER@CBN%
Rs0~53%eYrd8mt^7Z6]iTF+(EWfJ9zaK-iTV.C\y<pjxsg-b$f4ia>
--------------------------------------------------------
128 bit encrypted signature, crack if you can
|
|
|
|
|
Poor design is still poor design whether its for you or a thousand people.
only two letters away from being an asset
|
|
|
|
|
Now I have to wonder about your intent and motives...
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Hi,
I would like to create application that support main menus, toolbar and popup menus.
I know I can define one function and related all events ‘Click’ to this function.
I would like to define shortcut, tooltip and image for each GUI interface such as main men, tool bar and popup menu.
Is there an option to define it one time and relate it to each control?
I know I have in Borland type call ‘Action’ that can define the event function and property such as tooltip, shortcut and then define the action in each control
That way I define it one time and not three times for each option in GUI
Thanks
Ronen
|
|
|
|
|
Ronenb wrote: Is there an option to define it one time and relate it to each control?
Sure, you can create one method and point all of your events to it. That's about it, really.
Christian Graus
Driven to the arms of OSX by Vista.
|
|
|
|
|
Hi
OK and what about the definition of the shortcut and tooltip?
Ronen
|
|
|
|
|
The tooltip you can assign in the properties of the control, same place as the event handler goes. But, you do have to do that for each menu item/button/etc. Same for the shortcut.
Christian Graus
Driven to the arms of OSX by Vista.
|
|
|
|
|
Hello all,
I have a region that I have crated by combining and excluding GraphicsPath objects.
Now, I want to draw the region's outline, not fill it as it is.
I can't find any way to do that...
Anyone has any ideas???
Thanks.
|
|
|
|
|
The Graphics' DrawPath method draws the outline, FillPath draws filled shapes,so just go for the first one.
Regards,
Lev
|
|
|
|
|
I have a region, not a Graphics path.
The region is a result of a few action taken on GraphicPath objects.
A region only has a Fill method, not a Draw method.
|
|
|
|
|
I'm sorry, I misunderstood you, I googled a little, and it seems that there is no cheap way to do it.
It is possible to convert the Region to Path and draw the path by using Region.GetRegionScans which will return an array of rectangles approximating the region. But I think this is a quite expensive method. I believe it would be better to start with GraphicsPath instead, of course if it is possible in your case.
Regards,
Lev
|
|
|
|
|
Byte b= 0xff;
Byte c= 0x82;
Byte is 8 bit unsigned interger .Why is it initialized as above?
Thanks
|
|
|
|
|
hung1984 wrote: Byte is 8 bit unsigned interger .Why is it initialized as above?
I dont see anything wrong. What do you see wrong?
If they were 8 bit signed integers, then yes, we would/could have a problem.
xacc.ide - now with TabsToSpaces support IronScheme - 1.0 beta 1 - out now! ((lambda (x) `((lambda (x) ,x) ',x)) '`((lambda (x) ,x) ',x))
|
|
|
|
|
What do you think is wrong with it? Since both of those values are 8-bit values, written in hexadecimal, I don't see what the problem is.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
