Re: Native code references

2010-08-03 Thread Stephen Price
Ah nice, bit of lateral thinking there. I added them as Linked files so that the actual dll could remain where it is (and if it's updated it will automatically pick up the change) Many thanks, I think that's a little cleaner than the post build script. more visible too. cheers, Stephen On Tue,

Re: Mixing development software versions

2010-08-03 Thread Joseph Clark
I've had no problems mixing different versions of Visual Studio (2008 2010) and the .NET Framework (2, 3 4) on the one machine. Can't vouch for Silverlight though/ HTH, Joe. On Wed, Aug 4, 2010 at 9:20 AM, Greg Keogh g...@mira.net wrote: Folks, I’m preparing for the big migration of all

Re: Mixing development software versions

2010-08-03 Thread David Richards
Greg, I haven't experienced your specifi problem since I'm still using VS2008 on XP but I do work exclusively in VMs so I tell you what little relevant iinfo I can offer. For the mouse jittering, chech the hardware acceleration options (you may have already tried this). No idea where in Win7

RE: Mixing development software versions

2010-08-03 Thread Michael O'Dea-Jones
Hi Greg, Another thought: I have been using Sun Virtual Box (now Oracle Virtual Box) for all my development without any problems all year. All host PCs\Laptops are Win 7 64 bit. I can create 32 or 64 bit VM's. I can even create a 64 bit VM and run it inside a 32 bit host. The best part is

Rules regarding modifying members acces modifer through inheritence

2010-08-03 Thread Arjang Assadi
Are there any rules/guide lines / rules of thumb regarding modifying members access modifiers through inheritance? I can only think of LSP that one should not reduce access level of members in a child class respect to it's parent. What about increasing the access level? e.g. having a protected

Re: Rules regarding modifying members acces modifer through inheritence

2010-08-03 Thread Michael Minutillo
Hi Arjang, You can always create new members in the derived class which access the protected/internal members in the base class so widening the access levels should be fine. Remember that these access modifiers are really about intent not security. Anyone can use still reflection-fu to bypass

Re: Rules regarding modifying members acces modifer through inheritence

2010-08-03 Thread Arjang Assadi
On 4 August 2010 13:32, David Richards ausdot...@davidsuniverse.com wrote: Wouldn't increasing access technically just be adding a member to the subclass?  A member that, publicly anyway, the superclass didn't have. Yes, but I have seen cases where a member is declared protected and to access

Re: Mixing development software versions

2010-08-03 Thread Grant Molloy
Greg, Ensure that you have the VMWare Tools installed in the VM Client. Grant On Wed, Aug 4, 2010 at 9:20 AM, Greg Keogh g...@mira.net wrote: Folks, I’m preparing for the big migration of all of my projects to VS2010, Framework 4 and Silverlight 4. I built a Win7 in WMWare with the latest

Re: Rules regarding modifying members acces modifer through inheritence

2010-08-03 Thread David Richards
Keep in mind that what we're doing is creating a new class, not modifying the original class. We're not making the member public, we're creating a new public member in a new class that just happens to have the same name as a protected member in the base class. Would you feel better about it if