http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Thanks Oren, I've done some googling and found this : http://codebetter.com/blogs/darrell.norton/archive/2004/02/16/7354.aspx in darrell norton's blog (check out the comments) seams like I'm not the only one that had / has this problem (the post regards nunit but the problem is that same) anyway renaming the exe to dll over and over again kinda misses the whole idea (at least for me) i have decided to start by moving the logic of the new screens to a different project (DLL) hopefully it will not force me to migrate large portions of the code :) Thanks again http://ayende.com/2623/vb-user-group-talks-summary#comment3http://ayende.com/2623/vb-user-group-talks-summary#comment3Mon, 23 Jul 2007 17:46:55 GMTYes, You can rename the exe to a dll, and then it will work http://ayende.com/2623/vb-user-group-talks-summary#comment2http://ayende.com/2623/vb-user-group-talks-summary#comment2Mon, 23 Jul 2007 16:41:19 GMTHi, My functions are inside a very old - production !! - Legacy code -executable in vs2003 ( vb.net ). I have started a new C# project (.net .1.1) and tried to reference the exe in order to add some unit testing to this monster but it seems that i can't reference an exe in vs2003 !!! moving functions out of the main project is probably out of the question right now (so does migrating to vs2005). Is there a way to hook mbunit (or any other unit testing platform) to an vs2003 exe ? http://ayende.com/2623/vb-user-group-talks-summary#comment1http://ayende.com/2623/vb-user-group-talks-summary#comment1Mon, 23 Jul 2007 15:18:17 GMT