rallou24 Δημοσ. 10 Απριλίου 2007 Δημοσ. 10 Απριλίου 2007 Kalispera kai xronia polla. Diabazo kairo tora ta minimata sas kai mia pou katalaba oti oi perissoteroi eiste foberoi gnostes tha ithela na rotiso ki ego kati kai an xerete mou lete. agorasa laptop me proegatestimena ta vista. Perasa ti vb 6 alla den trexei sosta emfanizei kapoio problima me ta ole objects. mipos xerei kapoios apo esas an boro na kano kati? euxaristo!!
omen34 Δημοσ. 10 Απριλίου 2007 Δημοσ. 10 Απριλίου 2007 Χρόνια πολλά !!! Εμένα δεν μου έκατσε ούτε το 6 ούτε το 8 σε Vista Ultimate x32 Greek
random Δημοσ. 11 Απριλίου 2007 Δημοσ. 11 Απριλίου 2007 το Visual Studio 6 σαν πακέτο, δεν υποστηρίζεται πιά, και αποτυγχάνει η εγκατασταση, ισως λογω της παλιας ms java που περιέχει. VC++ 6, και άλλα που περιέχονται μέσα θεωρούνται απο την Ms νεκρά. Η VB6 σαν standalone installation υποτιθεται οτι δουλεύει, και η ms θα την υποστηρίζει μεχρι το 2008. σαν μέρος του VS6 (custom install) μαλλον θα εχει το προβλημα. στην τελική η Ms για τα Vista συνεχίζει την υποστήριξη μονο για : VB6, Foxpro 9, και VS 2005 SP1 (όχι σκέτο, μονο με το sp). http://www.itwriting.com/blog/?p=167 http://msdn2.microsoft.com/en-us/vstudio/aa948854.aspx http://blogs.msdn.com/jeffabraham/archive/2006/11/16/visual-studio-on-windows-vista.aspx Mike, here's the response I got from the VB team on this:Weʼve been testing the Visual Basic 6.0 SP6 runtime and IDE on Vista builds since earlier this year. Both run and install successfully on Vista RTM and are supported per the support statement posted at http://msdn2.microsoft.com/en-us/vbrun/ms788708.aspx. The Visual Basic 6.0 IDE and SP6 setup needs to be run with UAC on, with the local user running as Admin, running with elevated privileges (right click on the setup exe and select “Run As Administrator…”. Visual Basic 6.0 applications need to be run under the same security/runtime settings (UAC/Admin/Elevated). φαντάζομαι θα υπάρχουν και πολλές αλλες πληροφορίες εκει έξω... και τυχαίως έπεσα και σε ενα ποστ που με κανει να σκέφτομαι.... WTF were they thinking????? Are the people that run Microsoft NUTS, or what? Donʼt call your Windows app UpdateAnything I wrote a little Windows utility that updates a file. Itʼs safe and harmless; it just modifies a file which is in my user documents folder. I called the utility UpdateMSI. Under Vista with UAC enabled, running this app throws up a dialog: An unidentified program wants access to your computer But why? Simple: Vista inspects the name of the executable, notes that it includes the word “update”, and concludes that it needs local administrator rights. On the face of it, this is silly. First of all, Vista is wrong: my app does not need admin rights. Second, it is infuriating that I am not given any choice in the matter. The UAC dialog says “Cancel” or “Allow”. It does not include the option to run with my normal user rights. Microsoft did this in an effort to detect setup applications; the word “setup” has the same effect. It will trigger if the word is anywhere in the executable name. I tried it with WorldCupDatePicker.exe - same result. Surely it would not have been too hard to give the user a say in this? Just a checkbox that says “Let me run this how I want on my computer”? You can disable UAC of course; but Iʼm not going to do that; overall itʼs a good feature. http://www.itwriting.com/blog/?p=172
Προτεινόμενες αναρτήσεις
Αρχειοθετημένο
Αυτό το θέμα έχει αρχειοθετηθεί και είναι κλειστό για περαιτέρω απαντήσεις.