Hey Guys,
I think I know why it isn't working anymore...In WP8, CShellCromeAPI.dll only had an entrypoint called "Shell_PostMessageToast". In the WP 8.1 version there are 3 entrypoints: "Shell_PostMessageToast", "Shell_PostMessageToast2", and "Shell_RaiseToastNotifications".
I am guessing that starting with WP 8.1 it is now a 2-step process. You call "Shell_PostMessageToast" to put it on the stack, and then you call "Shell_RaiseToastNotifications" to fire them. It could also be as simple as replacing "Shell_PostMessageToast" with "Shell_PostMessageToast2". This is only speculation, but I can't test it as I only have a Windows 7 rig at work, so I can't compile against the WP 8.1 SDK.
If anyone with Visual Studio 2013 and Windows 8.1 with the WP 8.1 SDK installed wants to retarget the solution, we might be able to get it working again.
I think I know why it isn't working anymore...In WP8, CShellCromeAPI.dll only had an entrypoint called "Shell_PostMessageToast". In the WP 8.1 version there are 3 entrypoints: "Shell_PostMessageToast", "Shell_PostMessageToast2", and "Shell_RaiseToastNotifications".
I am guessing that starting with WP 8.1 it is now a 2-step process. You call "Shell_PostMessageToast" to put it on the stack, and then you call "Shell_RaiseToastNotifications" to fire them. It could also be as simple as replacing "Shell_PostMessageToast" with "Shell_PostMessageToast2". This is only speculation, but I can't test it as I only have a Windows 7 rig at work, so I can't compile against the WP 8.1 SDK.
If anyone with Visual Studio 2013 and Windows 8.1 with the WP 8.1 SDK installed wants to retarget the solution, we might be able to get it working again.