-1 from me. It's my debugger of choice. While an integrated solution would be better, I'm okay with the current project files. The default solution is nice to add the dissectors/files you're working on/consistently modify for quick reference. Outside of the debugger, I realize it is just a glorified text editor, but I'm okay with that.
-----Original Message----- From: Pascal Quantin <[email protected]> To: Developer support list for Wireshark <[email protected]> Sent: Tue, Sep 17, 2013 9:12 am Subject: Re: [Wireshark-dev] Removal of Visual Studio solution and project files Hi Graham, definitely a +1 for me. Regards, Pascal. 2013/9/17 Graham Bloice <[email protected]> As the Visual Studio solutions are not really maintained I'd like to delete them to prevent users from being confused when they try them and they don't work. If the project to get CMake working for windows builds is ever completed, then that will generate VS solutions and project files as required rendering the repository copies even more confusing. Any objections? -- Graham Bloice ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
