WPF: isolated storage file path too long -

I'm deploying my WPF app with ClickOnce when Visual Studio is developing locally, Code> isolated storage file.NetStoreFordom Domain () by calling and storing files in different storage. It works just fine and generated path

C: \ USER \ FREDERIC \ Epadata \ Local \ Separate Storage \ phqduaro.crw \ hux3pljr.cnx \ StrongName.kkulk3wafjkvclxpwvxmpvslqqwckuh0 \ Publisher.ui0lr4tpq53mz2v2c0uqx21x Ze0w22gq \ files \ filerefData \ - + 581750116 (189 characters)

But when I posted my app with ClickOnce, the resulting path becomes too long, resulting in a When creating separate directoryNotFoundException , the storage directory generated with ClickOnce is:

C: \ Users \ Frederick \ AppData \ Local \ Apps \ 2.0 \ Data \ OQ0LNXJT.R5V \ 8539ABHC ODN \ exqu'tion_e07264ceafd7486e_0001.0000_b8f01b38216164a0 \ Data \ StrongName.wy0cojdd3mpvq45404l3gxdklugoanvi \ Publisher.ui0lr4tpq53mz2v2c0uqx21xze0w22gq \ Files \ FilerefData \ - + 581750116 (247 characters)

When I browse the folders all directories exist but the last directory. Then when the windows tell me while trying to create a folder at this place, I can not create a directory because the resulting path name will be too long.

How can I reduce the path generated by IsolatedStorage?

"itemprop =" text ">

Well I found out this windows file system has a range of (around 250 character limit) And you can not select or configure the path of separate stores.

I can 'fix' the problem by changing the different storage scope from the domain ... not the right solution, but I will do it now