We have an application which is only 32bit. We have some customers which are using Microsoft Outlook 64 Bit (365, 2016, 2019 Version). Operating System is Windows 10 64 Bit. The thing is that you can add the attachement in our software automatically to outlook. It opens outlook window automatically with the attachement you can just have to write the text.
I could solve some problems by adding some registry keys for the outlook 32bit edition.
It is programmed in delphi and the function is mapisendmail
Normally it shows an error that the standard e-mail client is not configured.
now for 64bit there is no solution for windows 64bit with outlook64 bit. I have tried several things like outlook64bridge etc. but nothing works.
Is it possible to solve this problem on user side?
Thanks
Related
I have a visual basic(.vbp) desktop application, actually an excel add-ins, it is in VB 2006 and for 32 bit.
I need to upgrade it so it can work with 64 bit, is it possible to do so and how. please guide I have already searched on all internet.
Visual Basic 6 (which came out in 1998, not 2006) predates 64-bit Windows development, and certainly predates it being a normal thing. (Windows XP 64-bit for Itanium was released in 2001, and it didn't get much use.) VB6 can only create 32-bit DLLs and Executables. In order to create a 64-bit application, you will need to recreate the program in a more modern programming environment.
Some of the older versions of Visual Basic .NET have built-in tools to assist with the migration, which can help with some automated translation from VB6 to VB.NET. But, you'd still need to do some amount of manual work to convert it, and thoroughly test for your use cases.
Microsoft no longer supports VB6 development and support from Microsoft has already stopped. But VB6 applications still run on Windows 8.1. See also this article titled "Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1".
When would a VB6 application stop running on Windows? Is there any official statement from Microsoft or any clue about the same?
EDIT:
In this link, the Visual Studio team has mentioned that, "It will be supported at least through 2024". But it's not clear whether they said it's supported in Windows 8 till 2024 or in future release of windows OS too.
The "2024" means as part of Windows 8. The link says the VB6 runtime is part of Windows and therefore will be supported in the same way as the rest of Windows. For example Windows 8 will be supported until 2024 because that's the support lifecycle for Windows 8.
EDIT: Microsoft have now said the VB6 runtime is officially part of Windows 10 too.
EDIT: the VB6 IDE (not runtime) is no longer officially supported on any version of Windows, but there are ways to get it to work on Windows 7 and 8.
Uservoice: The VB6 runtime it is still a component of the Windows operating
system and is a component shipped in Windows 8.1. It will be supported
at least through 2024
It seems clear they mean VB6 will be supported through 2024, not just VB6 on Windows 8 (whose mainstream support ends 6 years earlier anyway).
The VB6 programming language installs and runs on Windows 7, 8.x and 10.
There is a utility to install it here: VB6 IDE install utility
It is in Microsoft's interests for VB6 applications to run in Windows 10 and so they probably will. The same is probably true of most old application frameworks: Microsoft works hard to maintain compatibility. The IDE runs on Windows 7 (not sure about 8 or 10).
However, just because Microsoft says VB6 will run it doesn't mean your particular application will work, particularly if you use third party components. You should at least be thinking about migrating to another development environment.
From what I heard, VB6 applications still work on Windows 10 technical preview. I've seen no official statement yet, but it would seem that VB6 will stay supported for at least a few years.
Microsoft have just stated for VB6 programming on Windows 10:-
"Windows is committed to compatibility. The Windows compatibility team
has been looking at user telemetry and reacting to feedback from
Windows Insiders to ensure that existing apps work well with Windows
10. Windows 10 is designed to run Windows 8.1 and Windows Phone 8.1 software programs. And yes, everyone’s favorite VB6 Runtime will
continue to work, too. In the near future, the compat team will go
more in-depth on this topic on Blogging Windows."
Everyone's favorite VB6 programming on Windows 10
So VB6 programming will work on Windows 10, as does VBA programming.
They also state that 'Project Centennial' Universal Windows Platform Bridge will work with VB6 code.
Instructions for installing the VB6 IDE are available here...
In my personal experience if you build a dll in VB6 and add it as a component to COM Plus in Server 2016 it just won't add. You will get an error such as the following, even for a 'Hello World' component.
A registry value was changed while installing the following component
into a COM+ Application. If you are experiencing activation problems
with this component then please check the registry value for the
following key.
Component: C:\temp\Project1.dll
Registry Key:
CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Process Name: RunDll32.exe Comsvcs.dll file version: not loaded
There is a project to provide a new language "RADBasic" which is intended to be compatible with the VB6 programming language.
New language compatible with VB6 programming
Looks like Microsoft just extended VB6 runtime support out to Windows 11 and Server 2022. No such luck for the IDE though.
Read more from Microsoft here:
https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6-support-policy
I have a VSTO add-in created using VS2010. I am developing the VSTO application using a 32 bit windows XP machine. I have created a 32 bit VS installer to deploy this add-in for all 32 bit office excel applications. The add-in works fine in all environments when i perform the installation on per user basis. The add-in loads in 32 bit excel 2010 on windows 7 for the every one option(all users). But the excel add-in failed to load for the all users option in a 32 bit office 2007 machine in windows 7. The registry entires on 2007 machine getting created under the HKLM\Software\Wow6432Node\Microsoft\Office\Excel\Addins. But when excel loads the add-in is not getting loaded by default. The excel add-in is showing up in the disable items list. Even try to select the add-in from the list, then also the add-in not getting loaded.
If anyone can provide support which will be of great help.
I dont know how to do it with VS installer, but for current users the addins entry will be created here
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\14.0\Excel\Addins
and for all users on that machine will be created here
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Excel\Addins
More information is here
As per requirement we have written one custom GINA. I have observed one interesting behavior in Windows XP 32 Bit(SP2). Customized GINA internally calls windows default Windows GINA (msgina.dll) and shows one extra window as per our requirement.
I used to do remote desktop to XP machine from my machine. After replacing Windows GINA with customized GINA I tried to log off from the XP Machine (I am Using Remote Desktop Connection to log in), Log off completes successfully (After showing saving your settings, Closing network connections etc) and I will get log in screen which we get during log on, this is not expected compared to other flavors of Windows OD.
Where as in other operating systems such as Windows XP 64 Bit/ Windows 2003 32/64 Bit even after replacing the Windows Gina with custom GINA remote desktop session closes after log off from the machine. I have tried installing Novell GINA on Windows XP 32 Bit but I have not find any issue with that.
I have Tried upgrading XP SP2 to SP3, still I am facing the same issue.
Has anyone else faced such issues when working with Windows GINA?
I cannot say that I had the same issues. Are you passing most of the functions through to msgina or do you do a lot of custom processing (and replacing the original code)?
My custom GINA was a very shallow wrapper of existing functionality and worked perfectly fine on Windows 2000, XP and 2003.
However, as to the differences in behavior: XP x64 is based on the Windows 2003 Server code base. So this could well explain some of the similarities between those and differences to "vanilla" XP.
Is the Windows 7 Home Premium sufficient for software development?
Development would be in Visual Studio 2010.
I'm on a budget so would rather purchase 'Home Premium' rather than 'Professional' or 'Ultimate'.
The Microsoft site says there is next to nothing functionality wise between them that developers would miss. Can anyone confirm or deny?
BTW. Does it come with a version of IIS?
I realize that this is not a technical question. But it is important to me and I'm sure other developers wonder the same thing.
Cheers,
-- Lee
Yes. I write software using VS 2010 in WIndows 7 Home Premium without any trouble.
Basically, yes, it's totally sufficient.
A big upside to professional edition, though, is that it comes with Windows XP mode, essentially a virtual machine with a built-in XP installation (and included license). That can come in handy if you do web development (test things in IE6/7) or need to test applications in the old XP GUI.
Windows XP mode can also be a lifesaver if you need to run older applications that won't run properly in 7. I personally would consider choosing the Professional Edition for that reason.
Don't purchase either, instead buy a MAPS subscription from them. In the UK these cost £199 p.a. (I imagine less in the states) for which you get virtually everything you're likely to need except Visual Studio. Currently you get
10 licences for MS Office 2007
10 for Project
10 for Visio
10 for Outlook
10 for Mappoint (North America only)
1 for Office Communications Server plus 10 CALS
10 for Windows 7 Professional
1 for Windows 7 Ultimate
1 for Windows Server 2008 R2, plus 10 Server CALS and 10 Terminal Server CALS
1 for Windows Web Server 2008 R2
1 for Windows Home Server 2008 R2
1 for Windows Business Server
1 for Windows Exchange server plus 10 CALS
1 for Windows Office Sharepoint, plus 10 CALS
1 for WIndows SQL Server standard plus 10 CALS
Plus a bunchload of other odds and sods servers and products of lesser interest.
MAPS is such good value - and I'm by no means a Microsoft fan - that purchase is pretty much a no-brainer for any software developer who runs Windows in any form.
UPDATE: Since I wrote this Microsoft now offer a Developer version of MAPS which replaces some of the more esoteric servers with Visual Studio. You still get the Office, Windows and SQL Server licences, which makes it just about perfect for any developer.
What you won't find on the Microsoft site, but on Wikipedia, is a nice Comparison Chart.
Compared to Professional, the Home Premium edition lacks:
support for more than 16 GB of memory: start worrying about that in a few years' time
network support in the Backup and Restore Center: not a problem if you handle your own backups
Remote Desktop server: not a problem if you develop only locally
some advanced disk management stuff: not a problem
features for a company network environment: not a problem
Windows XP mode: handy if you want to test on XP, but can be replaced by e.g. VMWare running an XP installation
Multilingual User Interface support: handy if you want to develop and test multilingual desktop applications
In conclusion: Professional may have some additional value if you develop Windows desktop applications for a diverse audience. If not, go for Home Premium.
Since you specifically asked:
Installing IIS 7.5 on Windows 7 Home Premium, Home Basic, or Home Starter (TechNet)
I guess in the past there were issues with developing for IIS on XP Home, but it looks like you can install IIS 7.5 on ANY version of Windows 7, including Starter, which I am surprised to see. I thought Starter was short of being useless for developers.
I agree with Pekka about XP Mode in Pro and Ultimate coming in handy if you need it. Sounds like Brian is already doing it and its working fine (I'm on Vista Ultimate until next week).
Yes. The OS you use really has little to do with development, unless you're targetting something specific to a version or edition of Windows (rare).