Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. The Weird and The Wonderful
  4. Alien Assembly Search

Alien Assembly Search

Scheduled Pinned Locked Moved The Weird and The Wonderful
csharpdotnetvisual-studiowinformslounge
2 Posts 2 Posters 5 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    Brady Kelly
    wrote on last edited by
    #1

    I have a general R&D solution I use to fiddle and explore various technicalities in. I add little disposable projects here and there as I need to explore some CLR or language feature or something. I only have one project at a time configured to build, the one I'm busy on, so I don't get dependency problems etc. So, I add a little WinForms project to test aspects of inheritence, and I hit F5 to run it, but this damn Assembly Search dialogue pops up, defaulted to a TestDriven.NET assembly. I check the key mapping for F5 and it's normal. I exit VS and start again, with the same damn Assembly Search dialogue invading my precious peace. I disable TestDriven.NET and on trying again I still get this hell spawn dialogue popping up. Then I notice I have an AssemblySearch project in the solution, :-O, and it's set as the Startup Project :-O I didn't expect it do do anything because it's excluded from the solution build, but, it wasn't building, just running.

    J 1 Reply Last reply
    0
    • B Brady Kelly

      I have a general R&D solution I use to fiddle and explore various technicalities in. I add little disposable projects here and there as I need to explore some CLR or language feature or something. I only have one project at a time configured to build, the one I'm busy on, so I don't get dependency problems etc. So, I add a little WinForms project to test aspects of inheritence, and I hit F5 to run it, but this damn Assembly Search dialogue pops up, defaulted to a TestDriven.NET assembly. I check the key mapping for F5 and it's normal. I exit VS and start again, with the same damn Assembly Search dialogue invading my precious peace. I disable TestDriven.NET and on trying again I still get this hell spawn dialogue popping up. Then I notice I have an AssemblySearch project in the solution, :-O, and it's set as the Startup Project :-O I didn't expect it do do anything because it's excluded from the solution build, but, it wasn't building, just running.

      J Offline
      J Offline
      John R Shaw
      wrote on last edited by
      #2

      That happens. ;) I discovered that same thing a while back, the thing that bothers me most is having to mark side projects (tests) to no build or vise-versa. It is irritating to have all subprojects rebuilt when I only want to rebuild the current one, especially if the current one is trying to test a piece of code that is causing an error in one of the other projects.

      INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups